Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 396fc49f4199b18370059eb8e775a41a4008e5e5681403d7df6ef71fae4b13d2

Tx prefix hash: 692d44aa19cec0ee00f3d9987a54f14e54f215f28092e8a85e054dee8fdb0474
Tx public key: eed8ecb008d0b83cf6042d976ad5463235e878af9eb5623f6107b00200362e24
Timestamp: 1771377939 Timestamp [UTC]: 2026-02-18 01:25:39 Age [y:d:h:m:s]: 00:276:18:41:11
Block: 1480146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203348 RingCT/type: yes/0
Extra: 01eed8ecb008d0b83cf6042d976ad5463235e878af9eb5623f6107b00200362e24021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 065c0e7d2300b7d8215dda9c8640abf485f05e076fe2ae83f33ec4269e54d37a 0.000600000000 1969510 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": 1480156, "vin": [ { "gen": { "height": 1480146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "065c0e7d2300b7d8215dda9c8640abf485f05e076fe2ae83f33ec4269e54d37a" } } ], "extra": [ 1, 238, 216, 236, 176, 8, 208, 184, 60, 246, 4, 45, 151, 106, 213, 70, 50, 53, 232, 120, 175, 158, 181, 98, 63, 97, 7, 176, 2, 0, 54, 46, 36, 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: