Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91d149e6256ac1423e1e95abd6dcc0689980171e55fbbc2d3d06a1c9277ebefe

Tx prefix hash: 274dea789fe10f465c3b4e3859bd41d9ebed7ae1a1c8bcf5e53791864cb7966a
Tx public key: abf9ce3a71876c1c45e6424ce48ecd54126aa27f5788794dcbcc01df321b4f2d
Timestamp: 1762828133 Timestamp [UCT]: 2025-11-11 02:28:53 Age [y:d:h:m:s]: 00:041:10:19:22
Block: 1409501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29658 RingCT/type: yes/0
Extra: 01abf9ce3a71876c1c45e6424ce48ecd54126aa27f5788794dcbcc01df321b4f2d021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea211305f4d4b2dbcd92e0eebb8234001bac2c5ba39da0da30a191bd085a6696 0.600000000000 1897948 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": 1409511, "vin": [ { "gen": { "height": 1409501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea211305f4d4b2dbcd92e0eebb8234001bac2c5ba39da0da30a191bd085a6696" } } ], "extra": [ 1, 171, 249, 206, 58, 113, 135, 108, 28, 69, 230, 66, 76, 228, 142, 205, 84, 18, 106, 162, 127, 87, 136, 121, 77, 203, 204, 1, 223, 50, 27, 79, 45, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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