Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e165e3b32b7f8e7d7cdee1649c761696e76586b82f910aa9fc1919ff13dffa9b

Tx prefix hash: 431748d3312748f3bb1f2415334e43239e46bd1443469bd474b80725bcb065a0
Tx public key: b0b423c8ceaf5f78a266aaf927db6e0702a8618b7147d05a7106214fcfb275c1
Timestamp: 1712059006 Timestamp [UCT]: 2024-04-02 11:56:46 Age [y:d:h:m:s]: 01:215:09:50:15
Block: 991691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412647 RingCT/type: yes/0
Extra: 01b0b423c8ceaf5f78a266aaf927db6e0702a8618b7147d05a7106214fcfb275c102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5bf9996516b03f1f8646e7408525cfd3757b55ca02f80767f64f7d05682541a 0.600000000000 1452027 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": 991701, "vin": [ { "gen": { "height": 991691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5bf9996516b03f1f8646e7408525cfd3757b55ca02f80767f64f7d05682541a" } } ], "extra": [ 1, 176, 180, 35, 200, 206, 175, 95, 120, 162, 102, 170, 249, 39, 219, 110, 7, 2, 168, 97, 139, 113, 71, 208, 90, 113, 6, 33, 79, 207, 178, 117, 193, 2, 17, 0, 0, 0, 4, 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