Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b222408f8174c0bc4a22ea8b66d639527a739bc4d06d2f734f8ff66dde5c17b

Tx prefix hash: 29af5450f25fa828b2c25e0e30ed2efaa4432c66cfd5afb1c01a4434913152f9
Tx public key: 387d6898e591f3e2056cb5a8eebca7f54b1d38f1dea4623481e168edd9e0395e
Timestamp: 1707554635 Timestamp [UCT]: 2024-02-10 08:43:55 Age [y:d:h:m:s]: 01:090:16:45:57
Block: 954367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325891 RingCT/type: yes/0
Extra: 01387d6898e591f3e2056cb5a8eebca7f54b1d38f1dea4623481e168edd9e0395e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a2343df67e1f02740e243a3064085abb8b6dcf6005e23501b0373ce4de52892 0.600000000000 1413647 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": 954377, "vin": [ { "gen": { "height": 954367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a2343df67e1f02740e243a3064085abb8b6dcf6005e23501b0373ce4de52892" } } ], "extra": [ 1, 56, 125, 104, 152, 229, 145, 243, 226, 5, 108, 181, 168, 238, 188, 167, 245, 75, 29, 56, 241, 222, 164, 98, 52, 129, 225, 104, 237, 217, 224, 57, 94, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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