Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfd17e37dd008aae862514524bdbdae79fbeaae272e606910338b46b4e0fb53e

Tx prefix hash: 0d0f0adc819621c545f3721db55cd949080078039ffb5f4e4cf53e0278652a61
Tx public key: 69f482feb7e0c39ea168f0d7b25faf548a2fb77ae316a392589d807d0de7dc7d
Timestamp: 1787242732 Timestamp [UTC]: 2026-08-20 16:18:52 Age [y:d:h:m:s]: 00:093:07:47:19
Block: 1617591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 65903 RingCT/type: yes/0
Extra: 0169f482feb7e0c39ea168f0d7b25faf548a2fb77ae316a392589d807d0de7dc7d020819262448b8e12d1a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 145f3951087673415411445b8fcbdcefc9378785d42c47fe5ca18d9713ff9dcb 0.000600000000 2107611 of 15 <b9>

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 dinastycoin-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": 1617601, "vin": [ { "gen": { "height": 1617591 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "145f3951087673415411445b8fcbdcefc9378785d42c47fe5ca18d9713ff9dcb", "view_tag": "b9" } } } ], "extra": [ 1, 105, 244, 130, 254, 183, 224, 195, 158, 161, 104, 240, 215, 178, 95, 175, 84, 138, 47, 183, 122, 227, 22, 163, 146, 88, 157, 128, 125, 13, 231, 220, 125, 2, 8, 25, 38, 36, 72, 184, 225, 45, 26 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: