Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69509edc19d505e9520ea662002ac0806d65033243470607633ed3885e9dc3cf

Tx prefix hash: 3da13cc22b6dc44a043ad2fc5ae5715e4851bcf611d8996371cfd6acf4f8421c
Tx public key: 432c2d2447a1403c97d34d249fafeeece60495c07cdeae56cd812985dc39f0f2
Timestamp: 1693138889 Timestamp [UCT]: 2023-08-27 12:21:29 Age [y:d:h:m:s]: 01:252:06:18:24
Block: 835035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441444 RingCT/type: yes/0
Extra: 01432c2d2447a1403c97d34d249fafeeece60495c07cdeae56cd812985dc39f0f2021100000008faf35c9c000000000000000000

1 output(s) for total of 1.049983523000 dcy

stealth address amount amount idx
00: 3580753b38c07eadbeeb929aaddb4150d8feef95aa5df7f5785780c8d364b0a9 1.049983523000 1287567 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": 835045, "vin": [ { "gen": { "height": 835035 } } ], "vout": [ { "amount": 1049983523, "target": { "key": "3580753b38c07eadbeeb929aaddb4150d8feef95aa5df7f5785780c8d364b0a9" } } ], "extra": [ 1, 67, 44, 45, 36, 71, 161, 64, 60, 151, 211, 77, 36, 159, 175, 238, 236, 230, 4, 149, 192, 124, 222, 174, 86, 205, 129, 41, 133, 220, 57, 240, 242, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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