Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5690b19718b29e299993f1bf41664775f8f67c0e618e73ffa61a06d2bb3c0ae

Tx prefix hash: c25eca3d682f90a8f140ccabb454f0704f50ac5fa1f8638e3dd4ddca4fd7b76f
Tx public key: 9f03cb86b36b3b0d12229286f286716401fc13e58a8622dd5d3361d31ed31e9f
Timestamp: 1732730333 Timestamp [UCT]: 2024-11-27 17:58:53 Age [y:d:h:m:s]: 00:337:06:34:45
Block: 1163001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238574 RingCT/type: yes/0
Extra: 019f03cb86b36b3b0d12229286f286716401fc13e58a8622dd5d3361d31ed31e9f0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d75a6467b9282cc0d97e1465506d17cab5cbc95c3ac3d97a2fdfcf86204220e0 0.600000000000 1648664 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": 1163011, "vin": [ { "gen": { "height": 1163001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d75a6467b9282cc0d97e1465506d17cab5cbc95c3ac3d97a2fdfcf86204220e0" } } ], "extra": [ 1, 159, 3, 203, 134, 179, 107, 59, 13, 18, 34, 146, 134, 242, 134, 113, 100, 1, 252, 19, 229, 138, 134, 34, 221, 93, 51, 97, 211, 30, 211, 30, 159, 2, 17, 0, 0, 0, 9, 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