Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc2ea1d624e8d3cd83bf3304644c4bfb93ebb047ea365864f4ab8f3c777aeb64

Tx prefix hash: d4f283e796648df57480ffe993d160f4c9043e28e4a8495be2d2eae9e0f0fe39
Tx public key: d6c74a707f57e6b205fcded2082d579b3d6833ab3816354030ee656def90a8b6
Timestamp: 1703360274 Timestamp [UCT]: 2023-12-23 19:37:54 Age [y:d:h:m:s]: 01:127:18:28:21
Block: 919598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352473 RingCT/type: yes/0
Extra: 01d6c74a707f57e6b205fcded2082d579b3d6833ab3816354030ee656def90a8b602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1d4d9b29f719ebcc332a9fd506fbd2aeb8d0332cb7144fc040a577fc3ee55df 0.600000000000 1377274 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": 919608, "vin": [ { "gen": { "height": 919598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1d4d9b29f719ebcc332a9fd506fbd2aeb8d0332cb7144fc040a577fc3ee55df" } } ], "extra": [ 1, 214, 199, 74, 112, 127, 87, 230, 178, 5, 252, 222, 210, 8, 45, 87, 155, 61, 104, 51, 171, 56, 22, 53, 64, 48, 238, 101, 109, 239, 144, 168, 182, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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