Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb796e769c28e24e5094bcd17b1e08d20fea4506ae75b6f95d35d438ce4fc32f

Tx prefix hash: 7c9401124961f39cf762e139fc8621500994d7f762c18d9725fb13e66d278e5f
Tx public key: e5c80bbae7c7e079c50d48f1eab17b63dae6b70f5a4ea4b227994fdee36fae2c
Timestamp: 1766153162 Timestamp [UCT]: 2025-12-19 14:06:02 Age [y:d:h:m:s]: 00:016:11:27:09
Block: 1437054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11802 RingCT/type: yes/0
Extra: 01e5c80bbae7c7e079c50d48f1eab17b63dae6b70f5a4ea4b227994fdee36fae2c0211000000077b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e674571b1d68400784a7f420a70b5e23f5b6b01b6054d8a4213c00dae81e052 0.600000000000 1925859 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": 1437064, "vin": [ { "gen": { "height": 1437054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e674571b1d68400784a7f420a70b5e23f5b6b01b6054d8a4213c00dae81e052" } } ], "extra": [ 1, 229, 200, 11, 186, 231, 199, 224, 121, 197, 13, 72, 241, 234, 177, 123, 99, 218, 230, 183, 15, 90, 78, 164, 178, 39, 153, 79, 222, 227, 111, 174, 44, 2, 17, 0, 0, 0, 7, 123, 30, 81, 172, 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