Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03af73a7df843133c6c5fc0c4cf8e35343cf4938b6b95a5ea481e2e6ae825652

Tx prefix hash: f690a3ad79914d826de934e5845c34d4de1a12466e90d6755d9c4ab0954cad56
Tx public key: 495c1d1b32ac26da1f63fcd3098937ba4defd61f52fbbcadc625d3d6b3ff0471
Timestamp: 1766604718 Timestamp [UCT]: 2025-12-24 19:31:58 Age [y:d:h:m:s]: 00:034:16:03:10
Block: 1440787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24653 RingCT/type: yes/0
Extra: 01495c1d1b32ac26da1f63fcd3098937ba4defd61f52fbbcadc625d3d6b3ff0471021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b506a07bfe4d928803423aa556685c14ff1bafead5addbe60c01fc93d5bf7fa5 0.600000000000 1929678 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": 1440797, "vin": [ { "gen": { "height": 1440787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b506a07bfe4d928803423aa556685c14ff1bafead5addbe60c01fc93d5bf7fa5" } } ], "extra": [ 1, 73, 92, 29, 27, 50, 172, 38, 218, 31, 99, 252, 211, 9, 137, 55, 186, 77, 239, 214, 31, 82, 251, 188, 173, 198, 37, 211, 214, 179, 255, 4, 113, 2, 17, 0, 0, 0, 9, 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