Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 601a89e878ac1e579b9269ccf1dfefec6017bbb1ece8bce58617c63290b4f3b1

Tx prefix hash: 62bf741e512961d8f9818c2277ad96a0e1b9c840a06d8dd3e8aa8a1acb070c0b
Tx public key: 7dbec216181118cdbdc52d9911e3fc56569af066ef5df5f965a2a1dd456bfeff
Timestamp: 1718841305 Timestamp [UCT]: 2024-06-19 23:55:05 Age [y:d:h:m:s]: 00:281:10:40:30
Block: 1047953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201110 RingCT/type: yes/0
Extra: 017dbec216181118cdbdc52d9911e3fc56569af066ef5df5f965a2a1dd456bfeff0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3e25b233f4f166fb4bc39fbd4a11b4163ec3ce25de3d7970f4ad5cc0a8735f3 0.600000000000 1517912 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": 1047963, "vin": [ { "gen": { "height": 1047953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3e25b233f4f166fb4bc39fbd4a11b4163ec3ce25de3d7970f4ad5cc0a8735f3" } } ], "extra": [ 1, 125, 190, 194, 22, 24, 17, 24, 205, 189, 197, 45, 153, 17, 227, 252, 86, 86, 154, 240, 102, 239, 93, 245, 249, 101, 162, 161, 221, 69, 107, 254, 255, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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