Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e4e80795612fc8396ccaafb9421992a1eea7592edc7b383a727ecdce92da32c

Tx prefix hash: 0e4d5ef83e2c85607b9f8bbe92d52f75cb4a7427a37ff16328b4d56f2d7c7216
Tx public key: 614b2b1bda4927d12216a8f30e9bd918dc957fc03a0103fe006e96327be8a1c7
Timestamp: 1761323403 Timestamp [UCT]: 2025-10-24 16:30:03 Age [y:d:h:m:s]: 00:076:00:28:09
Block: 1397046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54415 RingCT/type: yes/0
Extra: 01614b2b1bda4927d12216a8f30e9bd918dc957fc03a0103fe006e96327be8a1c7021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fba1822d8e42b94fe3a24232c90928b94420ff69b8be0c1cc76566fa56a513c 0.600000000000 1885337 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": 1397056, "vin": [ { "gen": { "height": 1397046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fba1822d8e42b94fe3a24232c90928b94420ff69b8be0c1cc76566fa56a513c" } } ], "extra": [ 1, 97, 75, 43, 27, 218, 73, 39, 209, 34, 22, 168, 243, 14, 155, 217, 24, 220, 149, 127, 192, 58, 1, 3, 254, 0, 110, 150, 50, 123, 232, 161, 199, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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