Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7358521a0c4e50e8dfa01c6703229b6cd8ac29c48616ef314122b3e1a8d80f40

Tx prefix hash: e444b99e663fbecda31da76afdd6a2d197abf947df0a1da1ea74af199e6d9ea2
Tx public key: 8f8b24e8a45a910fa3fe5b7ad61830011048e0c557cc32fee09e18d18522a940
Timestamp: 1765367480 Timestamp [UCT]: 2025-12-10 11:51:20 Age [y:d:h:m:s]: 00:030:00:21:37
Block: 1430538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21499 RingCT/type: yes/0
Extra: 018f8b24e8a45a910fa3fe5b7ad61830011048e0c557cc32fee09e18d18522a940021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 770dfc17b13070d736e9933e4b11648a633e8f7bf468d6595a1bd62bcca9f910 0.600000000000 1919289 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": 1430548, "vin": [ { "gen": { "height": 1430538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "770dfc17b13070d736e9933e4b11648a633e8f7bf468d6595a1bd62bcca9f910" } } ], "extra": [ 1, 143, 139, 36, 232, 164, 90, 145, 15, 163, 254, 91, 122, 214, 24, 48, 1, 16, 72, 224, 197, 87, 204, 50, 254, 224, 158, 24, 209, 133, 34, 169, 64, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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