Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fc577932cb4c1f3fbb5769980e72a58db3f76967a7c24394feff49e1baf49c0

Tx prefix hash: f018fe6f91016db563400d35349cb9e87e18addbdbdc5d6e099dd7495b189695
Tx public key: aec0b4bd74363a676b0b91b3c9320cc910f00cc3a048e6741e611a48f559faba
Timestamp: 1756027487 Timestamp [UCT]: 2025-08-24 09:24:47 Age [y:d:h:m:s]: 00:094:04:27:27
Block: 1353321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67252 RingCT/type: yes/0
Extra: 01aec0b4bd74363a676b0b91b3c9320cc910f00cc3a048e6741e611a48f559faba021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c33c41d32a9167a95ff7ee18fcd18234cd94a9c15dd86c8f65dfaa2744d8c3c0 0.600000000000 1841296 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": 1353331, "vin": [ { "gen": { "height": 1353321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c33c41d32a9167a95ff7ee18fcd18234cd94a9c15dd86c8f65dfaa2744d8c3c0" } } ], "extra": [ 1, 174, 192, 180, 189, 116, 54, 58, 103, 107, 11, 145, 179, 201, 50, 12, 201, 16, 240, 12, 195, 160, 72, 230, 116, 30, 97, 26, 72, 245, 89, 250, 186, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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