Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f7e843bd9256cb0d5820dc331d1343178af3bfd45f72492190f2e1cb6e24f8a

Tx prefix hash: f85dc2ef4ac7d2cd5e8d56063eebb6d0d7788155f5fd7ece1b3857615c12db99
Tx public key: ea988c5e319e0974546c480a50a025029befaf42692c3d9d10467e4b38dbe610
Timestamp: 1737649371 Timestamp [UCT]: 2025-01-23 16:22:51 Age [y:d:h:m:s]: 00:328:02:26:30
Block: 1203683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232071 RingCT/type: yes/0
Extra: 01ea988c5e319e0974546c480a50a025029befaf42692c3d9d10467e4b38dbe6100211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72b2d9a261606eacdec11134bd871f6efdb2d97e5d342dd966548413d66f2fa8 0.600000000000 1690362 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": 1203693, "vin": [ { "gen": { "height": 1203683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72b2d9a261606eacdec11134bd871f6efdb2d97e5d342dd966548413d66f2fa8" } } ], "extra": [ 1, 234, 152, 140, 94, 49, 158, 9, 116, 84, 108, 72, 10, 80, 160, 37, 2, 155, 239, 175, 66, 105, 44, 61, 157, 16, 70, 126, 75, 56, 219, 230, 16, 2, 17, 0, 0, 0, 4, 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