Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8b4fbbfa9bf641809bd21cb4bf93260436d3ee0b080b81e27fc1aa550835d29

Tx prefix hash: cb9fa7cd2d1af52837b10aad717e47574066c012b162ff4ba29bb4dfe72e4367
Tx public key: 481ea5b9b5e68548839e640d750ccc601b5e0fe040ed6e619c6a90429f8b8e74
Timestamp: 1702698496 Timestamp [UCT]: 2023-12-16 03:48:16 Age [y:d:h:m:s]: 01:330:13:30:15
Block: 914115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495106 RingCT/type: yes/0
Extra: 01481ea5b9b5e68548839e640d750ccc601b5e0fe040ed6e619c6a90429f8b8e7402110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 943ce806f901e7d031bd3cb290ea5287139cd6185ba79099c844c9460aa2edda 0.600000000000 1371399 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": 914125, "vin": [ { "gen": { "height": 914115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "943ce806f901e7d031bd3cb290ea5287139cd6185ba79099c844c9460aa2edda" } } ], "extra": [ 1, 72, 30, 165, 185, 181, 230, 133, 72, 131, 158, 100, 13, 117, 12, 204, 96, 27, 94, 15, 224, 64, 237, 110, 97, 156, 106, 144, 66, 159, 139, 142, 116, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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