Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9e47558556b154cbfbeb24241d57cba8887a0a689afa841726418fb00d5674a

Tx prefix hash: aa1f9f19dc95726c9031780aa7761a494a5d6553006a0bab7207ddb57f6f5599
Tx public key: b1185e13c81c90f9d8b4fa779a1178310bf6f2c4b450e720c1f49df390bfdb09
Timestamp: 1752757953 Timestamp [UCT]: 2025-07-17 13:12:33 Age [y:d:h:m:s]: 00:083:06:32:00
Block: 1327434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58224 RingCT/type: yes/0
Extra: 01b1185e13c81c90f9d8b4fa779a1178310bf6f2c4b450e720c1f49df390bfdb0902110000001743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e40f1d323a62a6edf977a51eeb417d3e6435f7741e4dd19f363d4a938eb9f763 0.600000000000 1815189 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": 1327444, "vin": [ { "gen": { "height": 1327434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e40f1d323a62a6edf977a51eeb417d3e6435f7741e4dd19f363d4a938eb9f763" } } ], "extra": [ 1, 177, 24, 94, 19, 200, 28, 144, 249, 216, 180, 250, 119, 154, 17, 120, 49, 11, 246, 242, 196, 180, 80, 231, 32, 193, 244, 157, 243, 144, 191, 219, 9, 2, 17, 0, 0, 0, 23, 67, 132, 109, 102, 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