Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a65dc60942acbce39a3bf39462876a9b3bdc9c2f0a9a4ee73c9c2f7b3c1a43f3

Tx prefix hash: 97bf4bf11627d8962e4735036fc8386c3ee92314c5e58d29443635eb5464f0bc
Tx public key: 0f5652d924971362b4ea10fb9d6469b1579c951b355aa3fcaaf1fccb10d9a3b1
Timestamp: 1721362428 Timestamp [UCT]: 2024-07-19 04:13:48 Age [y:d:h:m:s]: 01:111:09:25:37
Block: 1068864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338099 RingCT/type: yes/0
Extra: 010f5652d924971362b4ea10fb9d6469b1579c951b355aa3fcaaf1fccb10d9a3b102110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86225cc6bf6b326e7255c79432b34db7d87dee1d7e6a9976eb96db156c8fd048 0.600000000000 1540061 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": 1068874, "vin": [ { "gen": { "height": 1068864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86225cc6bf6b326e7255c79432b34db7d87dee1d7e6a9976eb96db156c8fd048" } } ], "extra": [ 1, 15, 86, 82, 217, 36, 151, 19, 98, 180, 234, 16, 251, 157, 100, 105, 177, 87, 156, 149, 27, 53, 90, 163, 252, 170, 241, 252, 203, 16, 217, 163, 177, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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