Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d67fad1e97edc33bfc853d1c7b36acf51769c248e68fcad17c0126a569ec9116

Tx prefix hash: 21c1854248d93ea797cff4d6b5f5a5f621e85498152a068ab3c1110417c5bfed
Tx public key: 2a9461d493c622a3a462d12be525d25c9e3a871c1d8fcee4e00a67ff53a79f1e
Timestamp: 1702024524 Timestamp [UCT]: 2023-12-08 08:35:24 Age [y:d:h:m:s]: 01:100:22:02:59
Block: 908533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333264 RingCT/type: yes/0
Extra: 012a9461d493c622a3a462d12be525d25c9e3a871c1d8fcee4e00a67ff53a79f1e02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 791ebac73f233b311761ed88b7c51a93a5625b2f913cf2c51a14435630f52971 0.600000000000 1365566 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": 908543, "vin": [ { "gen": { "height": 908533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "791ebac73f233b311761ed88b7c51a93a5625b2f913cf2c51a14435630f52971" } } ], "extra": [ 1, 42, 148, 97, 212, 147, 198, 34, 163, 164, 98, 209, 43, 229, 37, 210, 92, 158, 58, 135, 28, 29, 143, 206, 228, 224, 10, 103, 255, 83, 167, 159, 30, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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