Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7505310bf35ce3b4ba43622b415b391d8748dd78c3b30df88670db44615cb1d9

Tx prefix hash: 41814fc480f4c0360dcfc91919a732dfaad4a48e0b81b05b820be273869f90e2
Tx public key: c32b48e42b37a46d4cd290a841e08a77a511b58d122e5f840d2264f064de5a71
Timestamp: 1756181777 Timestamp [UCT]: 2025-08-26 04:16:17 Age [y:d:h:m:s]: 00:078:16:48:56
Block: 1354598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56166 RingCT/type: yes/0
Extra: 01c32b48e42b37a46d4cd290a841e08a77a511b58d122e5f840d2264f064de5a710211000000062609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdd9abc4a2e8aeeda940d2ef932d104222c7a811ef60dca7dbf76b672f837772 0.600000000000 1842589 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": 1354608, "vin": [ { "gen": { "height": 1354598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdd9abc4a2e8aeeda940d2ef932d104222c7a811ef60dca7dbf76b672f837772" } } ], "extra": [ 1, 195, 43, 72, 228, 43, 55, 164, 109, 76, 210, 144, 168, 65, 224, 138, 119, 165, 17, 181, 141, 18, 46, 95, 132, 13, 34, 100, 240, 100, 222, 90, 113, 2, 17, 0, 0, 0, 6, 38, 9, 179, 160, 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