Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 964f0a752ca92e0fdf4426c382b29fe0dce1572595839481c2d6fbbf0c014071

Tx prefix hash: 0b74b094a171190d2363cae42f226d20908e7ed7b029479b6becbff2055e6348
Tx public key: 2a40af15cde6517a77c8e9c6d0a2caf67a363e87bb1c1132eab4d45dce3a5ce2
Timestamp: 1711988197 Timestamp [UCT]: 2024-04-01 16:16:37 Age [y:d:h:m:s]: 01:065:02:39:08
Block: 991102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307567 RingCT/type: yes/0
Extra: 012a40af15cde6517a77c8e9c6d0a2caf67a363e87bb1c1132eab4d45dce3a5ce202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9b4c75c9ac533dc6e6ea951610b7b00cffbb8d4254184ba534e20d617dbc4ac 0.600000000000 1451436 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": 991112, "vin": [ { "gen": { "height": 991102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9b4c75c9ac533dc6e6ea951610b7b00cffbb8d4254184ba534e20d617dbc4ac" } } ], "extra": [ 1, 42, 64, 175, 21, 205, 230, 81, 122, 119, 200, 233, 198, 208, 162, 202, 246, 122, 54, 62, 135, 187, 28, 17, 50, 234, 180, 212, 93, 206, 58, 92, 226, 2, 17, 0, 0, 0, 2, 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