Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c20bf804b6c1898dd3b69a4bc7ee4a78adf125762ebcbdbfce8a2a7c4ddef632

Tx prefix hash: 752ece1281c5b93524078ffdd4c66fcd4b9e30577fa4442ac8a832ed01f81054
Tx public key: 28e27e04ffe6a82c41d615d3151645bae959d55ea3b6702296de48e0ba3ccc84
Timestamp: 1771287504 Timestamp [UTC]: 2026-02-17 00:18:24 Age [y:d:h:m:s]: 00:273:09:32:22
Block: 1479404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200901 RingCT/type: yes/0
Extra: 0128e27e04ffe6a82c41d615d3151645bae959d55ea3b6702296de48e0ba3ccc84021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9e7bda337375743642b9e2a77486975cf5f89d29feaf160aeff4ce566f594c5a 0.000600000000 1968752 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": 1479414, "vin": [ { "gen": { "height": 1479404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e7bda337375743642b9e2a77486975cf5f89d29feaf160aeff4ce566f594c5a" } } ], "extra": [ 1, 40, 226, 126, 4, 255, 230, 168, 44, 65, 214, 21, 211, 21, 22, 69, 186, 233, 89, 213, 94, 163, 182, 112, 34, 150, 222, 72, 224, 186, 60, 204, 132, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: