Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 820ef8c5641fb169a37355f75dd1f42dfdbd698b2736d69ed941df3797933074

Tx prefix hash: 6c0e48af4bb74a4d87e8dbf6c33042e9b09f57a30028ae4d24555e9b0061751b
Tx public key: 84c751e995ad23f016b84267e303f8e6b7cc47c33f61bd4acd43814ff3aa2b4f
Timestamp: 1738425293 Timestamp [UCT]: 2025-02-01 15:54:53 Age [y:d:h:m:s]: 00:292:06:32:27
Block: 1209878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206652 RingCT/type: yes/0
Extra: 0184c751e995ad23f016b84267e303f8e6b7cc47c33f61bd4acd43814ff3aa2b4f0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44b2822232ed649bbfc6636bee83448e939e06e8f4b01dd5dc0115c56b9d67d8 0.600000000000 1696625 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": 1209888, "vin": [ { "gen": { "height": 1209878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44b2822232ed649bbfc6636bee83448e939e06e8f4b01dd5dc0115c56b9d67d8" } } ], "extra": [ 1, 132, 199, 81, 233, 149, 173, 35, 240, 22, 184, 66, 103, 227, 3, 248, 230, 183, 204, 71, 195, 63, 97, 189, 74, 205, 67, 129, 79, 243, 170, 43, 79, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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