Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 356e84f8aa146e6417bae4fd5f46eb9514d5820651411c65e2b6e6d51e6d25ca

Tx prefix hash: ad292eb5fa34474f3790f7c53155ce49b3817c1e4b8b2475c9529004a16a069e
Tx public key: 09b58122781d16284ad543cfe634e94c01fcf618db1f5bbc77bb3458e02a5a1d
Timestamp: 1711245309 Timestamp [UCT]: 2024-03-24 01:55:09 Age [y:d:h:m:s]: 00:360:15:40:54
Block: 984994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257859 RingCT/type: yes/0
Extra: 0109b58122781d16284ad543cfe634e94c01fcf618db1f5bbc77bb3458e02a5a1d0211000000030424019c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 080b942fc4c3bda013d154093107b3cb5f14e0297a058a67fe7877948fef51ac 0.600000000000 1445199 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": 985004, "vin": [ { "gen": { "height": 984994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "080b942fc4c3bda013d154093107b3cb5f14e0297a058a67fe7877948fef51ac" } } ], "extra": [ 1, 9, 181, 129, 34, 120, 29, 22, 40, 74, 213, 67, 207, 230, 52, 233, 76, 1, 252, 246, 24, 219, 31, 91, 188, 119, 187, 52, 88, 224, 42, 90, 29, 2, 17, 0, 0, 0, 3, 4, 36, 1, 156, 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