Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 826c4bb0166ea2f10805986293ae25b62721f17f9f2b3b6bae90e6cb67b3c4ea

Tx prefix hash: 945bb0bacb524e76ece8b62a504e04ca2b308a9673cbe5a90ba20978a1e86cf5
Tx public key: 9e32cfb9f957fb3217f82e3d966f3255a2ae77c6cf10ed2d77604731ae2f14e6
Timestamp: 1751635812 Timestamp [UCT]: 2025-07-04 13:30:12 Age [y:d:h:m:s]: 00:139:12:03:41
Block: 1318634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97982 RingCT/type: yes/0
Extra: 019e32cfb9f957fb3217f82e3d966f3255a2ae77c6cf10ed2d77604731ae2f14e6021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f369a31f576fed3a1ccf2c66662d5bacb168304927f086cb49612a654df1221e 0.600000000000 1806319 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": 1318644, "vin": [ { "gen": { "height": 1318634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f369a31f576fed3a1ccf2c66662d5bacb168304927f086cb49612a654df1221e" } } ], "extra": [ 1, 158, 50, 207, 185, 249, 87, 251, 50, 23, 248, 46, 61, 150, 111, 50, 85, 162, 174, 119, 198, 207, 16, 237, 45, 119, 96, 71, 49, 174, 47, 20, 230, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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