Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c74d3ce2d4aadc4647e4d3f6b7cb2092246515ae23f4128a73c29e91d74630

Tx prefix hash: 33718e4dfec473e2e560214ff20362c8afc2f5f45fe1be350236449b37f2654f
Tx public key: bf126e1076666b4aa5f1c23496fc245fbe88061023f5a82408ef9f9f995e6930
Timestamp: 1725983132 Timestamp [UCT]: 2024-09-10 15:45:32 Age [y:d:h:m:s]: 00:166:20:37:14
Block: 1107162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119049 RingCT/type: yes/0
Extra: 01bf126e1076666b4aa5f1c23496fc245fbe88061023f5a82408ef9f9f995e693002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c89bcd823ad98745d7725780a49184f7b5cd1f8bd5e724592e2a3c6270ec60d5 0.600000000000 1584769 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": 1107172, "vin": [ { "gen": { "height": 1107162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c89bcd823ad98745d7725780a49184f7b5cd1f8bd5e724592e2a3c6270ec60d5" } } ], "extra": [ 1, 191, 18, 110, 16, 118, 102, 107, 74, 165, 241, 194, 52, 150, 252, 36, 95, 190, 136, 6, 16, 35, 245, 168, 36, 8, 239, 159, 159, 153, 94, 105, 48, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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