Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cdea50ff6dac50b714d205546bbecf9c19d3e46b6be75f760a18e3921757e7c

Tx prefix hash: f1b9c66ca03e8c12d03376307f455ea01df0a0b734d3f8e7998fad3d75bc8b34
Tx public key: 9eb679cfe9a8f7f0c5523632f2ccb77fdfe1f5838ceca723ce9506099503eacd
Timestamp: 1719494257 Timestamp [UCT]: 2024-06-27 13:17:37 Age [y:d:h:m:s]: 00:284:22:07:43
Block: 1053358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203587 RingCT/type: yes/0
Extra: 019eb679cfe9a8f7f0c5523632f2ccb77fdfe1f5838ceca723ce9506099503eacd0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1233e26016e660bb7b12a39c257f1d64be3afeff44ec44817985eb35002f7a78 0.600000000000 1523705 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": 1053368, "vin": [ { "gen": { "height": 1053358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1233e26016e660bb7b12a39c257f1d64be3afeff44ec44817985eb35002f7a78" } } ], "extra": [ 1, 158, 182, 121, 207, 233, 168, 247, 240, 197, 82, 54, 50, 242, 204, 183, 127, 223, 225, 245, 131, 140, 236, 167, 35, 206, 149, 6, 9, 149, 3, 234, 205, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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