Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c88f08f0b48f6a33f4a7a88baeb8af6b7577fcf47f0bf5e8b9141da47f92c854

Tx prefix hash: eeabc44e230d34b68f0006eeece0c19d9b72530ee76daf5496180518e9ad003a
Tx public key: 2f354735b5e80ebacdfcc9dc00bee16160857eac2cfd789726614a4248ccfaba
Timestamp: 1697063344 Timestamp [UCT]: 2023-10-11 22:29:04 Age [y:d:h:m:s]: 01:165:10:51:28
Block: 867601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379275 RingCT/type: yes/0
Extra: 012f354735b5e80ebacdfcc9dc00bee16160857eac2cfd789726614a4248ccfaba02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.818988417000 dcy

stealth address amount amount idx
00: 0e98417cfc4c54dde2a1f1ba584d3b0e85d2b7e670602e120ed974897747608b 0.818988417000 1322303 of 0

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": 867611, "vin": [ { "gen": { "height": 867601 } } ], "vout": [ { "amount": 818988417, "target": { "key": "0e98417cfc4c54dde2a1f1ba584d3b0e85d2b7e670602e120ed974897747608b" } } ], "extra": [ 1, 47, 53, 71, 53, 181, 232, 14, 186, 205, 252, 201, 220, 0, 190, 225, 97, 96, 133, 126, 172, 44, 253, 120, 151, 38, 97, 74, 66, 72, 204, 250, 186, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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