Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cac5f051e9f52e1bf9bfcd7e0e8d7704d29d6648b458eb51ff4bbb40e5b05e73

Tx prefix hash: 9180a911e580a9d61142e9491534e56011cab1aeb608e92e9e0e51f38bc17e87
Tx public key: afa5efbfd9f06260734d456391d509ec75ee6a97cebeeba43f2c89a714e2a3f9
Timestamp: 1753817702 Timestamp [UCT]: 2025-07-29 19:35:02 Age [y:d:h:m:s]: 00:017:23:08:37
Block: 1336150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11846 RingCT/type: yes/0
Extra: 01afa5efbfd9f06260734d456391d509ec75ee6a97cebeeba43f2c89a714e2a3f9021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d28a6c101d117bab842780199d3377c4dd0fa0ecf625947b9a4caf087332c22 0.600000000000 1823951 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": 1336160, "vin": [ { "gen": { "height": 1336150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d28a6c101d117bab842780199d3377c4dd0fa0ecf625947b9a4caf087332c22" } } ], "extra": [ 1, 175, 165, 239, 191, 217, 240, 98, 96, 115, 77, 69, 99, 145, 213, 9, 236, 117, 238, 106, 151, 206, 190, 235, 164, 63, 44, 137, 167, 20, 226, 163, 249, 2, 17, 0, 0, 0, 1, 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