Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 032d87481f0915225dd638c266ff7cab83b40a9b7e228f30fd61b450ad444d47

Tx prefix hash: e11535d908655c9ba5372f5b765d7b1a9119abf44dcfbcc22cb3f56bbd2ef08d
Tx public key: 27c5a09d284a00425de13251a4db8a31488417d248971523adb8c6d931a3c2a7
Timestamp: 1734038844 Timestamp [UCT]: 2024-12-12 21:27:24 Age [y:d:h:m:s]: 00:335:20:14:31
Block: 1173854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237525 RingCT/type: yes/0
Extra: 0127c5a09d284a00425de13251a4db8a31488417d248971523adb8c6d931a3c2a7021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d84a79e836326f4521b26d65fc412e80e5d488b674cbf3acfd1ae11885285020 0.600000000000 1659931 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": 1173864, "vin": [ { "gen": { "height": 1173854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d84a79e836326f4521b26d65fc412e80e5d488b674cbf3acfd1ae11885285020" } } ], "extra": [ 1, 39, 197, 160, 157, 40, 74, 0, 66, 93, 225, 50, 81, 164, 219, 138, 49, 72, 132, 23, 210, 72, 151, 21, 35, 173, 184, 198, 217, 49, 163, 194, 167, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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