Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce336eddfbe01474dcfd1fe466e72607be948e047f53c1bbb9419525ee0ae8fd

Tx prefix hash: 90b381738770e4d2d462d1a576b2defdf02991697158f4abdb8308dfea453122
Tx public key: c6fc8db03550dbccdef6f5c3e8cb97727681eef8cce54f0bb72796765aded42d
Timestamp: 1579446752 Timestamp [UCT]: 2020-01-19 15:12:32 Age [y:d:h:m:s]: 04:344:14:47:12
Block: 49247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135562 RingCT/type: yes/0
Extra: 01c6fc8db03550dbccdef6f5c3e8cb97727681eef8cce54f0bb72796765aded42d0211000000078a2ee0d9000000000000000000

1 output(s) for total of 421.526691386000 dcy

stealth address amount amount idx
00: 6af4268c441b42eee0bff6475bde0c77d6b056649e958d09f5bca6df7e0246a8 421.526691386000 91281 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": 49257, "vin": [ { "gen": { "height": 49247 } } ], "vout": [ { "amount": 421526691386, "target": { "key": "6af4268c441b42eee0bff6475bde0c77d6b056649e958d09f5bca6df7e0246a8" } } ], "extra": [ 1, 198, 252, 141, 176, 53, 80, 219, 204, 222, 246, 245, 195, 232, 203, 151, 114, 118, 129, 238, 248, 204, 229, 79, 11, 183, 39, 150, 118, 90, 222, 212, 45, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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