Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 476f0dcba6c9f51700320ffd0df4c26a267413f788d34d7b4c98a4d35138b204

Tx prefix hash: fee3e954bce25523984eb467db194903fa5e7a73a52a92242ceae9902634d6a3
Tx public key: 1629bfcf51f2b9e8651fe9f538356926c285b1ee1ac3b5a7b6a08358e9564793
Timestamp: 1577807045 Timestamp [UCT]: 2019-12-31 15:44:05 Age [y:d:h:m:s]: 05:131:06:27:29
Block: 35868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1243576 RingCT/type: yes/0
Extra: 011629bfcf51f2b9e8651fe9f538356926c285b1ee1ac3b5a7b6a08358e95647930211000000904fb58672000000000000000000

1 output(s) for total of 466.834332253000 dcy

stealth address amount amount idx
00: 05c55e1e124431fdd125bd2097a76077e06a1c3e52e666fd65b84e5521cd920a 466.834332253000 60561 of 0

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": 35878, "vin": [ { "gen": { "height": 35868 } } ], "vout": [ { "amount": 466834332253, "target": { "key": "05c55e1e124431fdd125bd2097a76077e06a1c3e52e666fd65b84e5521cd920a" } } ], "extra": [ 1, 22, 41, 191, 207, 81, 242, 185, 232, 101, 31, 233, 245, 56, 53, 105, 38, 194, 133, 177, 238, 26, 195, 181, 167, 182, 160, 131, 88, 233, 86, 71, 147, 2, 17, 0, 0, 0, 144, 79, 181, 134, 114, 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