Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e02e6f874b5d1c6e5e51a50ba69870ae46f07828022b87aba6cd5dc3cb318ed

Tx prefix hash: 39509d0660c451658d898b61df7aa474a4e03647d83b6861fdf2abdb77dadf54
Tx public key: 8ee4ecaa13103228f8c4d5ba81f165e68007717835b1cd106bb6404d75ebf126
Timestamp: 1750384542 Timestamp [UTC]: 2025-06-20 01:55:42 Age [y:d:h:m:s]: 00:330:21:53:48
Block: 1308746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226712 RingCT/type: yes/0
Extra: 018ee4ecaa13103228f8c4d5ba81f165e68007717835b1cd106bb6404d75ebf1260211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: edcea9ba3f819107823fbe0e5e2ce77c6eb2a8006c3df4217a35b7bfde5dffb0 0.000600000000 1796361 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": 1308756, "vin": [ { "gen": { "height": 1308746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edcea9ba3f819107823fbe0e5e2ce77c6eb2a8006c3df4217a35b7bfde5dffb0" } } ], "extra": [ 1, 142, 228, 236, 170, 19, 16, 50, 40, 248, 196, 213, 186, 129, 241, 101, 230, 128, 7, 113, 120, 53, 177, 205, 16, 107, 182, 64, 77, 117, 235, 241, 38, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: