Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b807aed59663898891237aac8edc0481602b280cb0a647f01eba25ed773397

Tx prefix hash: cf10303f5aea1f5ebe24520df8b3a752c73b656496d9696f0acb15505e864ed0
Tx public key: 769bb2dc09262f8f93512aed35187a56ceccd99ca5caf23d1624dbad0ece9bc9
Timestamp: 1766290774 Timestamp [UCT]: 2025-12-21 04:19:34 Age [y:d:h:m:s]: 00:006:19:49:46
Block: 1438202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4882 RingCT/type: yes/0
Extra: 01769bb2dc09262f8f93512aed35187a56ceccd99ca5caf23d1624dbad0ece9bc902110000000dd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8363d8a46a06e777b4d19d78c784fb4b0eb31ec35cf0f195c5a2888d9fb5ae3d 0.600000000000 1927019 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": 1438212, "vin": [ { "gen": { "height": 1438202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8363d8a46a06e777b4d19d78c784fb4b0eb31ec35cf0f195c5a2888d9fb5ae3d" } } ], "extra": [ 1, 118, 155, 178, 220, 9, 38, 47, 143, 147, 81, 42, 237, 53, 24, 122, 86, 206, 204, 217, 156, 165, 202, 242, 61, 22, 36, 219, 173, 14, 206, 155, 201, 2, 17, 0, 0, 0, 13, 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