Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 688dfeeffa0dac65fa3b0d4289e3269cde5c4b483e7264cdc70f4b880232bf23

Tx prefix hash: 0e00081867008afc1ec405a3928b6c4027752e136b29dd0fea6e804b199d74dc
Tx public key: 003a6a0779d0a05b974d9d8074a281ebe7749cb82af48defb990a216b5c507d3
Timestamp: 1738498099 Timestamp [UCT]: 2025-02-02 12:08:19 Age [y:d:h:m:s]: 00:292:12:13:41
Block: 1210482 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206823 RingCT/type: yes/0
Extra: 01003a6a0779d0a05b974d9d8074a281ebe7749cb82af48defb990a216b5c507d302110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73a772b394c67f767cc62596982dac1c6c54311f4d773266e40552075cbba012 0.600000000000 1697235 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": 1210492, "vin": [ { "gen": { "height": 1210482 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73a772b394c67f767cc62596982dac1c6c54311f4d773266e40552075cbba012" } } ], "extra": [ 1, 0, 58, 106, 7, 121, 208, 160, 91, 151, 77, 157, 128, 116, 162, 129, 235, 231, 116, 156, 184, 42, 244, 141, 239, 185, 144, 162, 22, 181, 197, 7, 211, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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