Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044d8fa110b05d831ec3f8b26fefd0f6fc9b47c6bf8ce9eea7bbd162d5cce63f

Tx prefix hash: 43e1c9d1c50957f67b6bd3e2d395ba33b6421b70b3b5e1ee27e423ec9fe1ab31
Tx public key: 7be632b8c603c99e883ff87987865c54128315fd602b7d95ab9e49f3c3d5b5a9
Timestamp: 1763553598 Timestamp [UCT]: 2025-11-19 11:59:58 Age [y:d:h:m:s]: 00:008:17:49:37
Block: 1415502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6266 RingCT/type: yes/0
Extra: 017be632b8c603c99e883ff87987865c54128315fd602b7d95ab9e49f3c3d5b5a90211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3358525a82f7e8d69b1a16d34ee6e67ae0ebb1313137424742054aafe2f123a 0.600000000000 1904003 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": 1415512, "vin": [ { "gen": { "height": 1415502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3358525a82f7e8d69b1a16d34ee6e67ae0ebb1313137424742054aafe2f123a" } } ], "extra": [ 1, 123, 230, 50, 184, 198, 3, 201, 158, 136, 63, 248, 121, 135, 134, 92, 84, 18, 131, 21, 253, 96, 43, 125, 149, 171, 158, 73, 243, 195, 213, 181, 169, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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