Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e03e7bf64f478f5cc41c487ce94625fa846fe943911a309a96c2be5a0b1ac42

Tx prefix hash: fd828340d83c53f687151994cf24a67c5087560d8a48f635ceba08d577934253
Tx public key: 447067e884c1aa0bcfb66c8f0ac8c4e75e52411d241ad65317d0ac211c751634
Timestamp: 1742234743 Timestamp [UCT]: 2025-03-17 18:05:43 Age [y:d:h:m:s]: 00:295:06:36:51
Block: 1241441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208816 RingCT/type: yes/0
Extra: 01447067e884c1aa0bcfb66c8f0ac8c4e75e52411d241ad65317d0ac211c75163402110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 556769a29c45d331c634bdfa4d596685b13e058a078c2c9268ac3c8c0816d864 0.600000000000 1728414 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": 1241451, "vin": [ { "gen": { "height": 1241441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "556769a29c45d331c634bdfa4d596685b13e058a078c2c9268ac3c8c0816d864" } } ], "extra": [ 1, 68, 112, 103, 232, 132, 193, 170, 11, 207, 182, 108, 143, 10, 200, 196, 231, 94, 82, 65, 29, 36, 26, 214, 83, 23, 208, 172, 33, 28, 117, 22, 52, 2, 17, 0, 0, 0, 12, 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