Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac5d4edfd5c7c65251308da0e7289ee582aec4ff6c7a20b606439104aade6f69

Tx prefix hash: 5c6656a84f1fdbbdfe5131c12ad7b573da741c82c40149728fca14c3e3e3dd15
Tx public key: 9b6f688930f4f9bcef37daff741c3452ef38ff8ec52771ea40b0e0eeacfe8445
Timestamp: 1744358026 Timestamp [UCT]: 2025-04-11 07:53:46 Age [y:d:h:m:s]: 00:216:20:52:12
Block: 1258995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152717 RingCT/type: yes/0
Extra: 019b6f688930f4f9bcef37daff741c3452ef38ff8ec52771ea40b0e0eeacfe8445021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a073460a043e44a69fdaa4b74616cf0f34f2ecf141d8536326f2f7f7301e0d8e 0.600000000000 1746134 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": 1259005, "vin": [ { "gen": { "height": 1258995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a073460a043e44a69fdaa4b74616cf0f34f2ecf141d8536326f2f7f7301e0d8e" } } ], "extra": [ 1, 155, 111, 104, 137, 48, 244, 249, 188, 239, 55, 218, 255, 116, 28, 52, 82, 239, 56, 255, 142, 197, 39, 113, 234, 64, 176, 224, 238, 172, 254, 132, 69, 2, 17, 0, 0, 0, 3, 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