Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 708fd3981f5e49cf77d604a8cbc8d4fb6dff93cd0714ee8e922079885685a619

Tx prefix hash: 076b7a2e09e00e21e90d4a927295f03a7b36811e01015675e9b619a7ee04790e
Tx public key: 8434c9448788b9e0474bd8718fcbbb94a08480802e1d9ee93d728a9b076a1a91
Timestamp: 1713978384 Timestamp [UCT]: 2024-04-24 17:06:24 Age [y:d:h:m:s]: 00:248:13:29:56
Block: 1007635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177905 RingCT/type: yes/0
Extra: 018434c9448788b9e0474bd8718fcbbb94a08480802e1d9ee93d728a9b076a1a910211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abe28a376c42e13392cf09b77b546af7473001f90d1143e602c01e2bc89334b2 0.600000000000 1469041 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": 1007645, "vin": [ { "gen": { "height": 1007635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abe28a376c42e13392cf09b77b546af7473001f90d1143e602c01e2bc89334b2" } } ], "extra": [ 1, 132, 52, 201, 68, 135, 136, 185, 224, 71, 75, 216, 113, 143, 203, 187, 148, 160, 132, 128, 128, 46, 29, 158, 233, 61, 114, 138, 155, 7, 106, 26, 145, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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