Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6c970a5fd49c10059b4a571fb5d7924cb0909bbba5223875ee1c10e247ff029

Tx prefix hash: b55bc63576f3aec506c08d8909b1740eeca99fc305da779ba29ffb94ebacfca7
Tx public key: 657ded5222acaaeb9416f6e377a791e568b5c7acad81a9a41242a1dd5fb37c59
Timestamp: 1696238114 Timestamp [UCT]: 2023-10-02 09:15:14 Age [y:d:h:m:s]: 01:197:08:24:00
Block: 860764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402095 RingCT/type: yes/0
Extra: 01657ded5222acaaeb9416f6e377a791e568b5c7acad81a9a41242a1dd5fb37c5902110000000133af99f4000000000000000000

1 output(s) for total of 0.862842620000 dcy

stealth address amount amount idx
00: c5be8303e5a2499794cf64e34c2f0ea5c6cf98a81a001e6a2b795a1afbc98487 0.862842620000 1315066 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": 860774, "vin": [ { "gen": { "height": 860764 } } ], "vout": [ { "amount": 862842620, "target": { "key": "c5be8303e5a2499794cf64e34c2f0ea5c6cf98a81a001e6a2b795a1afbc98487" } } ], "extra": [ 1, 101, 125, 237, 82, 34, 172, 170, 235, 148, 22, 246, 227, 119, 167, 145, 229, 104, 181, 199, 172, 173, 129, 169, 164, 18, 66, 161, 221, 95, 179, 124, 89, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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