Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16542c5dc39d62f2f947fe24e28dac19dcdb44f2282ff14f636db9b16037abf0

Tx prefix hash: 1b957f2ee10bd3099483f83625d25bbca2a75aa193c3aeab19ae2d149643cec0
Tx public key: 7764531d0f9aecdd24621fec64dc728c79453953389e945fa663243dce5dbf63
Timestamp: 1760539566 Timestamp [UTC]: 2025-10-15 14:46:06 Age [y:d:h:m:s]: 01:037:19:18:25
Block: 1390533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292961 RingCT/type: yes/0
Extra: 017764531d0f9aecdd24621fec64dc728c79453953389e945fa663243dce5dbf630211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fe6f3af6f6f24f642a0b0e363afebcc8c371a61b7945cc45d1e0007382ed7fc7 0.000600000000 1878778 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": 1390543, "vin": [ { "gen": { "height": 1390533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe6f3af6f6f24f642a0b0e363afebcc8c371a61b7945cc45d1e0007382ed7fc7" } } ], "extra": [ 1, 119, 100, 83, 29, 15, 154, 236, 221, 36, 98, 31, 236, 100, 220, 114, 140, 121, 69, 57, 83, 56, 158, 148, 95, 166, 99, 36, 61, 206, 93, 191, 99, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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: