Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e35ab45219a7e345bf49958c9e55ffc2183d6c3882879adb0632ca1682b5ca85

Tx prefix hash: b8bd9e462f6802143634a2a36304494a02ef3e6830f5918a12a2151529acd557
Tx public key: 9cff948b7604e8dd2096cf1dcb34ee3e8e36d4e28fca50d8e2653c9dd7fc5ca4
Timestamp: 1714977488 Timestamp [UCT]: 2024-05-06 06:38:08 Age [y:d:h:m:s]: 00:183:07:12:07
Block: 1015920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131203 RingCT/type: yes/0
Extra: 019cff948b7604e8dd2096cf1dcb34ee3e8e36d4e28fca50d8e2653c9dd7fc5ca40211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08b2216fceaf0b2619ef4e8c2aa1ee1ba1dadfe10c8418d4550b569edc9dc877 0.600000000000 1479363 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": 1015930, "vin": [ { "gen": { "height": 1015920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b2216fceaf0b2619ef4e8c2aa1ee1ba1dadfe10c8418d4550b569edc9dc877" } } ], "extra": [ 1, 156, 255, 148, 139, 118, 4, 232, 221, 32, 150, 207, 29, 203, 52, 238, 62, 142, 54, 212, 226, 143, 202, 80, 216, 226, 101, 60, 157, 215, 252, 92, 164, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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