Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a10316716fe3a9dbcaf719e3ee344bf28957faf8600de81dfdccb832803eb656

Tx prefix hash: 6edd5f735045e5d7325702a6b980dc7786b73c0ca7be154f8797c917f1b4b953
Tx public key: 2a93e50910345404ac0e7fbfcdeb7e0f7640675d59b5b1833fbc86f90ed7cd49
Timestamp: 1761103874 Timestamp [UCT]: 2025-10-22 03:31:14 Age [y:d:h:m:s]: 00:097:09:35:54
Block: 1395216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69544 RingCT/type: yes/0
Extra: 012a93e50910345404ac0e7fbfcdeb7e0f7640675d59b5b1833fbc86f90ed7cd49021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2f1a57097e0e0cad25666c518ff0e209d7ef94567a6e8417e6bc24dc3c8d6c7 0.600000000000 1883493 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": 1395226, "vin": [ { "gen": { "height": 1395216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2f1a57097e0e0cad25666c518ff0e209d7ef94567a6e8417e6bc24dc3c8d6c7" } } ], "extra": [ 1, 42, 147, 229, 9, 16, 52, 84, 4, 172, 14, 127, 191, 205, 235, 126, 15, 118, 64, 103, 93, 89, 181, 177, 131, 63, 188, 134, 249, 14, 215, 205, 73, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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