Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0ff489914590d1c8514c56bde8c72ccb41c7e9464c122e54b59ea0ac4bfd400

Tx prefix hash: 44db6a9434f9bdb1b9ad74be6b70842e530af54ad385b11a3e920c8118308f9a
Tx public key: a554324d3d05d603b091cbd09774586202188c7de7635cb66b317be09f8dd331
Timestamp: 1740929375 Timestamp [UCT]: 2025-03-02 15:29:35 Age [y:d:h:m:s]: 00:263:10:04:18
Block: 1230609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186007 RingCT/type: yes/0
Extra: 01a554324d3d05d603b091cbd09774586202188c7de7635cb66b317be09f8dd33102110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f254816ab35d3965c742198f6b7b38171b2da6bb63b8efe5a81eac4cb1ce4b7 0.600000000000 1717508 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": 1230619, "vin": [ { "gen": { "height": 1230609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f254816ab35d3965c742198f6b7b38171b2da6bb63b8efe5a81eac4cb1ce4b7" } } ], "extra": [ 1, 165, 84, 50, 77, 61, 5, 214, 3, 176, 145, 203, 208, 151, 116, 88, 98, 2, 24, 140, 125, 231, 99, 92, 182, 107, 49, 123, 224, 159, 141, 211, 49, 2, 17, 0, 0, 0, 13, 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