Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71765a92a430f591cfd47c96a21b9e35f1ea76770abd945fc21554a2db1765a2

Tx prefix hash: b842f164d8b13f4f6c56f2d3ee98a79c72e473ec8e599fb61e266ea333594a55
Tx public key: b5b9c0c83297e558b386fd6d95cc6f83bce72223f2380cffbee6d0f380a5befa
Timestamp: 1577713177 Timestamp [UTC]: 2019-12-30 13:39:37 Age [y:d:h:m:s]: 06:329:09:19:54
Block: 35064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1649086 RingCT/type: yes/0
Extra: 01b5b9c0c83297e558b386fd6d95cc6f83bce72223f2380cffbee6d0f380a5befa021100000005d81c26c0000000000000000000

1 output(s) for total of 0.469698601508 xmr

stealth address amount amount idx tag
00: 4c119ddd00d81e50a5914f01ed98be782820c830138c1192172b922850583c97 0.469698601508 59067 of 0 -

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": 35074, "vin": [ { "gen": { "height": 35064 } } ], "vout": [ { "amount": 469698601508, "target": { "key": "4c119ddd00d81e50a5914f01ed98be782820c830138c1192172b922850583c97" } } ], "extra": [ 1, 181, 185, 192, 200, 50, 151, 229, 88, 179, 134, 253, 109, 149, 204, 111, 131, 188, 231, 34, 35, 242, 56, 12, 255, 190, 230, 208, 243, 128, 165, 190, 250, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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: