Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c359d13d35fd0085e73debdc3299e47f50b651a13a878ef26e940b53cb0a508

Tx prefix hash: 23ca541aeae4ce88e52dcb5f94d023d72dac11b49073e821cd5b4b44481ee7d5
Tx public key: 1f11830eca3c0639aa50a5e68f50aefe0577de8b95bd2bff9aa12205cab08bc1
Timestamp: 1717887534 Timestamp [UTC]: 2024-06-08 22:58:54 Age [y:d:h:m:s]: 02:076:00:50:24
Block: 1040050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579504 RingCT/type: yes/0
Extra: 011f11830eca3c0639aa50a5e68f50aefe0577de8b95bd2bff9aa12205cab08bc10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 00e194643bae546a79a58a94a7df1f4d8375fc05733a8357f4819a52b4a6eca1 0.000600000000 1508705 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": 1040060, "vin": [ { "gen": { "height": 1040050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00e194643bae546a79a58a94a7df1f4d8375fc05733a8357f4819a52b4a6eca1" } } ], "extra": [ 1, 31, 17, 131, 14, 202, 60, 6, 57, 170, 80, 165, 230, 143, 80, 174, 254, 5, 119, 222, 139, 149, 189, 43, 255, 154, 161, 34, 5, 202, 176, 139, 193, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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: