Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 309cb0036b74ed1becc80c0e3daf73f2b1fe47943c103c49ecaa431216767fd5

Tx prefix hash: 47b68eb82b4d1df43a688350aabaabb12b5684c251f5defc98167c98be2d2973
Tx public key: eb3c1885dba2f81c6198ab0f4ba80cbbf1b683f72d5af765c1334d6dd2c0554d
Timestamp: 1754758877 Timestamp [UCT]: 2025-08-09 17:01:17 Age [y:d:h:m:s]: 00:008:01:25:30
Block: 1343601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5071 RingCT/type: yes/0
Extra: 01eb3c1885dba2f81c6198ab0f4ba80cbbf1b683f72d5af765c1334d6dd2c0554d021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d05d01ca7c120d5aaf5e8f83c4601b2d12354770e402bd1bf8b9b9c4fcd52b3 0.600000000000 1831442 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": 1343611, "vin": [ { "gen": { "height": 1343601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d05d01ca7c120d5aaf5e8f83c4601b2d12354770e402bd1bf8b9b9c4fcd52b3" } } ], "extra": [ 1, 235, 60, 24, 133, 219, 162, 248, 28, 97, 152, 171, 15, 75, 168, 12, 187, 241, 182, 131, 247, 45, 90, 247, 101, 193, 51, 77, 109, 210, 192, 85, 77, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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