Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 305a4ef45bc49899a2ca6fd3204b30814203c14f55e8be67d4b743fff92573ad

Tx prefix hash: 2bfe9b3ea017a238930ded09c4e75f0a70c1d08c714f38235a2bb3a03417d82d
Tx public key: 1c4ea0ed93fe53b6b6a3e5a8ad9a7920e7e0bfc75a25c3104091c1cd6c75ef96
Timestamp: 1743948085 Timestamp [UCT]: 2025-04-06 14:01:25 Age [y:d:h:m:s]: 00:226:06:22:54
Block: 1255582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159456 RingCT/type: yes/0
Extra: 011c4ea0ed93fe53b6b6a3e5a8ad9a7920e7e0bfc75a25c3104091c1cd6c75ef960211000000086c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0516a88478913004bf5ea511b729128dfe61d07fa0f1b3e458f3e46033fbfdd 0.600000000000 1742687 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": 1255592, "vin": [ { "gen": { "height": 1255582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0516a88478913004bf5ea511b729128dfe61d07fa0f1b3e458f3e46033fbfdd" } } ], "extra": [ 1, 28, 78, 160, 237, 147, 254, 83, 182, 182, 163, 229, 168, 173, 154, 121, 32, 231, 224, 191, 199, 90, 37, 195, 16, 64, 145, 193, 205, 108, 117, 239, 150, 2, 17, 0, 0, 0, 8, 108, 152, 170, 61, 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