Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e924704ba67a4dd4a97458eee0988fa3bdafe8e2d9df210b687c137c57ebcd43

Tx prefix hash: d516d908062a8c4dba0f2d5a2f8cf8d8149e1641333a24b3469ae19c0a308eb6
Tx public key: 6b23b081bdbb4be900d179b72ee280d37c904628132e750614e2f9d9ae34545f
Timestamp: 1746063885 Timestamp [UCT]: 2025-05-01 01:44:45 Age [y:d:h:m:s]: 00:197:03:01:13
Block: 1273107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138605 RingCT/type: yes/0
Extra: 016b23b081bdbb4be900d179b72ee280d37c904628132e750614e2f9d9ae34545f021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ee9b0eef8f1351a3134479a8f3c6c5d337e78a49139d7076125a1e84c48ac60 0.600000000000 1760386 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": 1273117, "vin": [ { "gen": { "height": 1273107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ee9b0eef8f1351a3134479a8f3c6c5d337e78a49139d7076125a1e84c48ac60" } } ], "extra": [ 1, 107, 35, 176, 129, 189, 187, 75, 233, 0, 209, 121, 183, 46, 226, 128, 211, 124, 144, 70, 40, 19, 46, 117, 6, 20, 226, 249, 217, 174, 52, 84, 95, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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