Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd95b6d0664e6c6b358cefba9af31c26839f1903819a9a285f09e2ea069bf543

Tx prefix hash: 0cbb528eb36cde56585173e812afdb5879568597cb4024894c9cc1a3442b57da
Tx public key: d8c8de18724ac34158c2994464a2f34f9b61249684a0b3e08eaff97b884a0b4a
Timestamp: 1724779662 Timestamp [UCT]: 2024-08-27 17:27:42 Age [y:d:h:m:s]: 01:070:09:43:30
Block: 1097168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308757 RingCT/type: yes/0
Extra: 01d8c8de18724ac34158c2994464a2f34f9b61249684a0b3e08eaff97b884a0b4a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e648ae51ff3f56936a1f82e0469f60fd22a3104f4a0ca29327b9a3b173fd21f4 0.600000000000 1572495 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": 1097178, "vin": [ { "gen": { "height": 1097168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e648ae51ff3f56936a1f82e0469f60fd22a3104f4a0ca29327b9a3b173fd21f4" } } ], "extra": [ 1, 216, 200, 222, 24, 114, 74, 195, 65, 88, 194, 153, 68, 100, 162, 243, 79, 155, 97, 36, 150, 132, 160, 179, 224, 142, 175, 249, 123, 136, 74, 11, 74, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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