Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4fde28e5d8d3db2e69f07ea7c40b17e79c0e6689ed4fc54d23ff26e11d1bc4c

Tx prefix hash: d5680aabb03bf365df9c2a838450c695c7e0647b0cb9157a7ad688e071beec1a
Tx public key: 57218da429f97807d3db79c72314d4cb863a2a69bf738edc85eb794b2e3d6488
Timestamp: 1750528260 Timestamp [UCT]: 2025-06-21 17:51:00 Age [y:d:h:m:s]: 00:190:16:54:09
Block: 1309918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134194 RingCT/type: yes/0
Extra: 0157218da429f97807d3db79c72314d4cb863a2a69bf738edc85eb794b2e3d64880211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a50abaeb0d20151390a731334e881008a82e7c9f528a0e0af73dfb62fc96289 0.600000000000 1797535 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": 1309928, "vin": [ { "gen": { "height": 1309918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a50abaeb0d20151390a731334e881008a82e7c9f528a0e0af73dfb62fc96289" } } ], "extra": [ 1, 87, 33, 141, 164, 41, 249, 120, 7, 211, 219, 121, 199, 35, 20, 212, 203, 134, 58, 42, 105, 191, 115, 142, 220, 133, 235, 121, 75, 46, 61, 100, 136, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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