Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 566c77813f7ea01500fa5a17c797d8d1e77b68d4768a108bf6377ddae74a5e30

Tx prefix hash: 9c91f776bd9b1556435cd8d055c9625a8b86caab44ea2e81bc7d0807803b55ad
Tx public key: 2a975fe407a0ec54b6669232ed96c5f3652d9e14b1b90edd975dedb671c37eb0
Timestamp: 1726441838 Timestamp [UCT]: 2024-09-15 23:10:38 Age [y:d:h:m:s]: 00:058:14:25:31
Block: 1110956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41899 RingCT/type: yes/0
Extra: 012a975fe407a0ec54b6669232ed96c5f3652d9e14b1b90edd975dedb671c37eb0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb0710df9f0fe26796c0820dfece46a6d326e02d823a9ee6384ecf59a93d8617 0.600000000000 1589749 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": 1110966, "vin": [ { "gen": { "height": 1110956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb0710df9f0fe26796c0820dfece46a6d326e02d823a9ee6384ecf59a93d8617" } } ], "extra": [ 1, 42, 151, 95, 228, 7, 160, 236, 84, 182, 102, 146, 50, 237, 150, 197, 243, 101, 45, 158, 20, 177, 185, 14, 221, 151, 93, 237, 182, 113, 195, 126, 176, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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