Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e453b22da8139dae3f4479f4ab4306f7c86204ecb014d03dd0ea9c440bb98ad8

Tx prefix hash: 2724ccf2d8d14350c3df510e17fbe2626eb8c32a6d0b84e74c6133cf579a5c62
Tx public key: e6ca04b5948f710a079639df167e780f247692ac06607a3717e7d6ecb899aa91
Timestamp: 1707002506 Timestamp [UCT]: 2024-02-03 23:21:46 Age [y:d:h:m:s]: 00:346:23:34:31
Block: 949784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248407 RingCT/type: yes/0
Extra: 01e6ca04b5948f710a079639df167e780f247692ac06607a3717e7d6ecb899aa9102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca13aa43578be8cadbe269b7e7058b9335d456a08b2a3bf1b8d056b3d1de75ad 0.600000000000 1408316 of 15

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": 949794, "vin": [ { "gen": { "height": 949784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca13aa43578be8cadbe269b7e7058b9335d456a08b2a3bf1b8d056b3d1de75ad" } } ], "extra": [ 1, 230, 202, 4, 181, 148, 143, 113, 10, 7, 150, 57, 223, 22, 126, 120, 15, 36, 118, 146, 172, 6, 96, 122, 55, 23, 231, 214, 236, 184, 153, 170, 145, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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