Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b01e708e8e6806284baef93161426f924ead048f4b690c4899ba864fcda8abe4

Tx prefix hash: f90b9b6f8e0c495a0a2077039d90f569b1118a5e27890fed9f7bd4c3df1be9e5
Tx public key: 18269bbac6c9d8e48aaa7dcd43b4878302d44b9df5bad118a33e54045ef33896
Timestamp: 1739531363 Timestamp [UTC]: 2025-02-14 11:09:23 Age [y:d:h:m:s]: 01:277:23:46:59
Block: 1219046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462789 RingCT/type: yes/0
Extra: 0118269bbac6c9d8e48aaa7dcd43b4878302d44b9df5bad118a33e54045ef33896021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 790fdfb1f079354d4d731554c51e2fd2107a48613cea2d677863caf42e3a4e4a 0.000600000000 1705869 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 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": 1219056, "vin": [ { "gen": { "height": 1219046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "790fdfb1f079354d4d731554c51e2fd2107a48613cea2d677863caf42e3a4e4a" } } ], "extra": [ 1, 24, 38, 155, 186, 198, 201, 216, 228, 138, 170, 125, 205, 67, 180, 135, 131, 2, 212, 75, 157, 245, 186, 209, 24, 163, 62, 84, 4, 94, 243, 56, 150, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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