Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971ce5d1e476e765b883be77d9b94abcebd6099ec9de8c34c48a622a8f46eb3b

Tx prefix hash: 6c3b459b48fb43e2bdb0ba56c801b573b8a30c886ad780e02de6665c1e5f22dd
Tx public key: 0d0970cee0fbf025234ced4431c54a08e35e229fa50b7034c82c59d75d9f2537
Timestamp: 1723304097 Timestamp [UCT]: 2024-08-10 15:34:57 Age [y:d:h:m:s]: 00:244:01:38:18
Block: 1084951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174317 RingCT/type: yes/0
Extra: 010d0970cee0fbf025234ced4431c54a08e35e229fa50b7034c82c59d75d9f253702110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba6951d6b5b55a073ad831aae31758aceb2d29d43fd8d9f690aab887a213394e 0.600000000000 1559410 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": 1084961, "vin": [ { "gen": { "height": 1084951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba6951d6b5b55a073ad831aae31758aceb2d29d43fd8d9f690aab887a213394e" } } ], "extra": [ 1, 13, 9, 112, 206, 224, 251, 240, 37, 35, 76, 237, 68, 49, 197, 74, 8, 227, 94, 34, 159, 165, 11, 112, 52, 200, 44, 89, 215, 93, 159, 37, 55, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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