Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a35227f22221038eabb03bf837ce64bbddf05b2d1ab56ef966b373c911c3b9a

Tx prefix hash: 0f265431d26f1ea79eed987a387852f3d615adb774997cd7c132480082b75d9f
Tx public key: a3c7ded4e97eff992d8f48a61392bbc62dee8d0be880f9f5bc59325f93504c32
Timestamp: 1708823558 Timestamp [UCT]: 2024-02-25 01:12:38 Age [y:d:h:m:s]: 01:037:16:04:35
Block: 964901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287932 RingCT/type: yes/0
Extra: 01a3c7ded4e97eff992d8f48a61392bbc62dee8d0be880f9f5bc59325f93504c3202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c361a66fdb5f842d68b65cb38904dfa18a4c8d9df7bc54cb7644fb65494a6cae 0.600000000000 1424644 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": 964911, "vin": [ { "gen": { "height": 964901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c361a66fdb5f842d68b65cb38904dfa18a4c8d9df7bc54cb7644fb65494a6cae" } } ], "extra": [ 1, 163, 199, 222, 212, 233, 126, 255, 153, 45, 143, 72, 166, 19, 146, 187, 198, 45, 238, 141, 11, 232, 128, 249, 245, 188, 89, 50, 95, 147, 80, 76, 50, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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