Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00302a3145a49531eef1ca137e028469f594642ce66bde894f724273ff6d40ab

Tx prefix hash: 40c1b93a9c34722984792ad612de0d523965afdac9e9d46c2262b5b4c8efed5b
Tx public key: 9e32f698620fb510c6f8ffdd33671ee42fdf3a62ab4fe6c5eb22e5b3a92debbc
Timestamp: 1749360502 Timestamp [UCT]: 2025-06-08 05:28:22 Age [y:d:h:m:s]: 00:155:19:46:31
Block: 1300417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109038 RingCT/type: yes/0
Extra: 019e32f698620fb510c6f8ffdd33671ee42fdf3a62ab4fe6c5eb22e5b3a92debbc02110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a4b88864041fb8c66f336227744dfc01303ebdf1d4845e1dcdb33c45098f470 0.600000000000 1787966 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": 1300427, "vin": [ { "gen": { "height": 1300417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a4b88864041fb8c66f336227744dfc01303ebdf1d4845e1dcdb33c45098f470" } } ], "extra": [ 1, 158, 50, 246, 152, 98, 15, 181, 16, 198, 248, 255, 221, 51, 103, 30, 228, 47, 223, 58, 98, 171, 79, 230, 197, 235, 34, 229, 179, 169, 45, 235, 188, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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