Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf54f703e54a3e461414fc1cc69487d9728951d79816ae81d8e1e44290d2b389

Tx prefix hash: 06e7ac3eba8b2896ab193b3ae39611c9a1acdb391d658e4e1f7076d03f6ab98c
Tx public key: cca2f33e97d8645f2701dc47c88ca5caa7be342559b0e97cd5cb4585b6410988
Timestamp: 1744819449 Timestamp [UCT]: 2025-04-16 16:04:09 Age [y:d:h:m:s]: 00:215:17:14:13
Block: 1262815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151899 RingCT/type: yes/0
Extra: 01cca2f33e97d8645f2701dc47c88ca5caa7be342559b0e97cd5cb4585b641098802110000001c6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fbe5b307d57a310cdd693de73f35a639ca57843a692da6cff45c02e744ebc89 0.600000000000 1749998 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": 1262825, "vin": [ { "gen": { "height": 1262815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fbe5b307d57a310cdd693de73f35a639ca57843a692da6cff45c02e744ebc89" } } ], "extra": [ 1, 204, 162, 243, 62, 151, 216, 100, 95, 39, 1, 220, 71, 200, 140, 165, 202, 167, 190, 52, 37, 89, 176, 233, 124, 213, 203, 69, 133, 182, 65, 9, 136, 2, 17, 0, 0, 0, 28, 108, 152, 170, 61, 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