Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 66d8314fabd2c251c1ebc1d316dcadea65b056bb9c94976674b7a380b83bda9d

Tx prefix hash: de8dff7fb3e0ee79e56e51f863c21d507d0327206e34fb279c65a4f0589454d7
Tx public key: 5458ea59d551087405008da5eeaa5abafa6db44e6806d8ad401fba5fe5f13d83
Timestamp: 1663294612 Timestamp [UCT]: 2022-09-16 02:16:52 Age [y:d:h:m:s]: 02:204:11:13:23
Block: 588856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 667432 RingCT/type: yes/0
Extra: 015458ea59d551087405008da5eeaa5abafa6db44e6806d8ad401fba5fe5f13d83021100000003faf35c9c000000000000000000

1 output(s) for total of 6.868718251000 dcy

stealth address amount amount idx
00: 0a59bb894a83e3d00e11819df37795dc374930dc92fa2cad6820898abff8c91d 6.868718251000 1023109 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 588866, "vin": [ { "gen": { "height": 588856 } } ], "vout": [ { "amount": 6868718251, "target": { "key": "0a59bb894a83e3d00e11819df37795dc374930dc92fa2cad6820898abff8c91d" } } ], "extra": [ 1, 84, 88, 234, 89, 213, 81, 8, 116, 5, 0, 141, 165, 238, 170, 90, 186, 250, 109, 180, 78, 104, 6, 216, 173, 64, 31, 186, 95, 229, 241, 61, 131, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8