Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43e4a7c66c36e1356d5d098877df777e9dd4743bf1d137e26533afb40ee00502

Tx prefix hash: 4178fa397d910120bc5e26c711618c66aa7ce8212c4236f0f523d1d7e9764389
Tx public key: 68b97f9f09237632082a4c783bfb1f8c5901bdf3c3115e0f3a3feb7966a015dc
Timestamp: 1762023124 Timestamp [UCT]: 2025-11-01 18:52:04 Age [y:d:h:m:s]: 00:006:13:05:36
Block: 1402835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4680 RingCT/type: yes/0
Extra: 0168b97f9f09237632082a4c783bfb1f8c5901bdf3c3115e0f3a3feb7966a015dc02110000000c25a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa749d4394bef47f3a845c30c8389ea7dc391aa637eadbfd33332bc51e5d86c9 0.600000000000 1891158 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": 1402845, "vin": [ { "gen": { "height": 1402835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa749d4394bef47f3a845c30c8389ea7dc391aa637eadbfd33332bc51e5d86c9" } } ], "extra": [ 1, 104, 185, 127, 159, 9, 35, 118, 50, 8, 42, 76, 120, 59, 251, 31, 140, 89, 1, 189, 243, 195, 17, 94, 15, 58, 63, 235, 121, 102, 160, 21, 220, 2, 17, 0, 0, 0, 12, 37, 163, 90, 15, 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