Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e024a6d9d088a1fd19f30dffb6f64eb7a8a3c58512e2a0d7a711a427b4f993bf

Tx prefix hash: 161bd8beb780e572350a67c94081f8152ca54cdf5ddcfc1e613052efddd6d034
Tx public key: c76fb8e8b7bdcbef22e5fc53539e8bacbe6a3c2336cfccab17fbeeff64d55b33
Timestamp: 1577171278 Timestamp [UCT]: 2019-12-24 07:07:58 Age [y:d:h:m:s]: 05:144:16:23:21
Block: 30472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1253299 RingCT/type: yes/0
Extra: 01c76fb8e8b7bdcbef22e5fc53539e8bacbe6a3c2336cfccab17fbeeff64d55b3302110000000b4ac5aa02000000000000000000

1 output(s) for total of 486.486720209000 dcy

stealth address amount amount idx
00: 5272c3e9b7b9c6b2b2c3bed981f67c180fba4dedbade6ce0228c347a510751d0 486.486720209000 50314 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": 30482, "vin": [ { "gen": { "height": 30472 } } ], "vout": [ { "amount": 486486720209, "target": { "key": "5272c3e9b7b9c6b2b2c3bed981f67c180fba4dedbade6ce0228c347a510751d0" } } ], "extra": [ 1, 199, 111, 184, 232, 183, 189, 203, 239, 34, 229, 252, 83, 83, 158, 139, 172, 190, 106, 60, 35, 54, 207, 204, 171, 23, 251, 238, 255, 100, 213, 91, 51, 2, 17, 0, 0, 0, 11, 74, 197, 170, 2, 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