Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f6635421c6a270e3fde248739b8075bd5631159849af51ffa3a99221ed13ed

Tx prefix hash: 3daffde46a11310bee958e2cf671b1fe8c7058c2e5070e24a4d34bf8779d6c87
Tx public key: 424dfb75e2bae924eead3299a9120668f748fd3404a7b0ee5ebd68f566c07a1a
Timestamp: 1707779493 Timestamp [UCT]: 2024-02-12 23:11:33 Age [y:d:h:m:s]: 01:064:12:55:33
Block: 956235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307176 RingCT/type: yes/0
Extra: 01424dfb75e2bae924eead3299a9120668f748fd3404a7b0ee5ebd68f566c07a1a0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67f586a1f7552da04bafa761357dc2fb25f9310fd3c2d73ea51f288fdcefc47f 0.600000000000 1415539 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": 956245, "vin": [ { "gen": { "height": 956235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67f586a1f7552da04bafa761357dc2fb25f9310fd3c2d73ea51f288fdcefc47f" } } ], "extra": [ 1, 66, 77, 251, 117, 226, 186, 233, 36, 238, 173, 50, 153, 169, 18, 6, 104, 247, 72, 253, 52, 4, 167, 176, 238, 94, 189, 104, 245, 102, 192, 122, 26, 2, 17, 0, 0, 0, 9, 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