Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 282675468a5b34b4e6bd2a65ad755b53cee30d7accf779e64260365303bc38f7

Tx prefix hash: d3305c3a382f0ebbfea44c31e000d5943324cadce78535cf3eeb49b3c6597b45
Tx public key: ddf7f04b4bd07d81406597a2fdf889c3843f5f4b35b4e0ac9e2e97aa681548b5
Timestamp: 1763270238 Timestamp [UCT]: 2025-11-16 05:17:18 Age [y:d:h:m:s]: 00:048:22:25:33
Block: 1413156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35053 RingCT/type: yes/0
Extra: 01ddf7f04b4bd07d81406597a2fdf889c3843f5f4b35b4e0ac9e2e97aa681548b502110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eaa0855e648b1380d0962d7cbe0a88b5ff59e2ed424425746dc9b263e9ea965 0.600000000000 1901633 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": 1413166, "vin": [ { "gen": { "height": 1413156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eaa0855e648b1380d0962d7cbe0a88b5ff59e2ed424425746dc9b263e9ea965" } } ], "extra": [ 1, 221, 247, 240, 75, 75, 208, 125, 129, 64, 101, 151, 162, 253, 248, 137, 195, 132, 63, 95, 75, 53, 180, 224, 172, 158, 46, 151, 170, 104, 21, 72, 181, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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