Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a4fc5be58e65b6042e4c9015a34a30336a5c6480b0d39459b464f201f2346ae

Tx prefix hash: c86e57c6aa300b2dde582471346f3498dc78b17eae8957ccd6170efe6005eae0
Tx public key: 1edc24dc4578dd79b9afad61a98c0c7e0fcb37c3388e834bbdcbd04f56f45148
Timestamp: 1738534840 Timestamp [UCT]: 2025-02-02 22:20:40 Age [y:d:h:m:s]: 00:329:19:41:46
Block: 1210785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233542 RingCT/type: yes/0
Extra: 011edc24dc4578dd79b9afad61a98c0c7e0fcb37c3388e834bbdcbd04f56f4514802110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d71639f0c301d85b367f8b7351d49b91938718042c812903fbac9cd0f47b6cd8 0.600000000000 1697540 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": 1210795, "vin": [ { "gen": { "height": 1210785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d71639f0c301d85b367f8b7351d49b91938718042c812903fbac9cd0f47b6cd8" } } ], "extra": [ 1, 30, 220, 36, 220, 69, 120, 221, 121, 185, 175, 173, 97, 169, 140, 12, 126, 15, 203, 55, 195, 56, 142, 131, 75, 189, 203, 208, 79, 86, 244, 81, 72, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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