Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e97d42441ede2a1cb0247d9ff027ff04ed94a715ac51e9683fdd9e003aed2e59

Tx prefix hash: 54f28b125e6369448f7f9b42d856878e5b35f95232fda876b4fa3f2f701c0482
Tx public key: 9df8e92cb70c6de64b5946b58a03f3aa86187f5a6d0bdae7410b839be4077416
Timestamp: 1697772205 Timestamp [UCT]: 2023-10-20 03:23:25 Age [y:d:h:m:s]: 01:173:07:24:41
Block: 873484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384884 RingCT/type: yes/0
Extra: 019df8e92cb70c6de64b5946b58a03f3aa86187f5a6d0bdae7410b839be4077416021100000003faf35c9c000000000000000000

1 output(s) for total of 0.783041771000 dcy

stealth address amount amount idx
00: fe93074c4b41b8f2f31bb8137b0e8a9bc0d7ea77b1e1d278d37751c8a52bbdf0 0.783041771000 1328634 of 0

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": 873494, "vin": [ { "gen": { "height": 873484 } } ], "vout": [ { "amount": 783041771, "target": { "key": "fe93074c4b41b8f2f31bb8137b0e8a9bc0d7ea77b1e1d278d37751c8a52bbdf0" } } ], "extra": [ 1, 157, 248, 233, 44, 183, 12, 109, 230, 75, 89, 70, 181, 138, 3, 243, 170, 134, 24, 127, 90, 109, 11, 218, 231, 65, 11, 131, 155, 228, 7, 116, 22, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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