Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38de907f29bbd71fca8c5ce6ae2fc9e561065acac0f0a75affb5e52a0a3d151c

Tx prefix hash: 4ec1e46d5ab4d7faca66d258a76a10e53903da451e80530c397dd6deccff4227
Tx public key: 90500159dd07037291692c8d6ac83d21dadb4c7610b8082adeb4da88644732e8
Timestamp: 1774760840 Timestamp [UTC]: 2026-03-29 05:07:20 Age [y:d:h:m:s]: 00:234:10:31:32
Block: 1508146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173072 RingCT/type: yes/0
Extra: 0190500159dd07037291692c8d6ac83d21dadb4c7610b8082adeb4da88644732e8021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e0c3554a8ef42075e5565e51fddaae1390ae50c165899d1e7318cd10e8a018f7 0.000600000000 1997898 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": 1508156, "vin": [ { "gen": { "height": 1508146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0c3554a8ef42075e5565e51fddaae1390ae50c165899d1e7318cd10e8a018f7" } } ], "extra": [ 1, 144, 80, 1, 89, 221, 7, 3, 114, 145, 105, 44, 141, 106, 200, 61, 33, 218, 219, 76, 118, 16, 184, 8, 42, 222, 180, 218, 136, 100, 71, 50, 232, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: