Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbce35df384affcb13a7074c9e6364bab0d1f33c4d5145a49abe7abbd520614a

Tx prefix hash: 188323659fefd31e41093af459a93da5d01fb61ff3399a4a0d4507a9b13495e0
Tx public key: 8c80144dc0f861a716bfdb9a75af4f4ef3edd1fa43060dc8379f572d13d0c138
Timestamp: 1700068377 Timestamp [UCT]: 2023-11-15 17:12:57 Age [y:d:h:m:s]: 01:208:10:11:30
Block: 892315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410183 RingCT/type: yes/0
Extra: 018c80144dc0f861a716bfdb9a75af4f4ef3edd1fa43060dc8379f572d13d0c138021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.678250281000 dcy

stealth address amount amount idx
00: 0692c105036505cb255f3b0bb8ac46d87cd3c62467065c0afd5d050a4f69be00 0.678250281000 1348422 of 0

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": 892325, "vin": [ { "gen": { "height": 892315 } } ], "vout": [ { "amount": 678250281, "target": { "key": "0692c105036505cb255f3b0bb8ac46d87cd3c62467065c0afd5d050a4f69be00" } } ], "extra": [ 1, 140, 128, 20, 77, 192, 248, 97, 167, 22, 191, 219, 154, 117, 175, 79, 78, 243, 237, 209, 250, 67, 6, 13, 200, 55, 159, 87, 45, 19, 208, 193, 56, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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