Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e1eb15343f9b364bb598315b7fb75017c1f45abb74cc797bc072d69abf07d29

Tx prefix hash: ded808ed577057462e3fdc54a61f6c2afdf84d3e25704cc4cccc8f92a89e9121
Tx public key: 0c36e6c71a993269b7362a0730251bfc158d9a6e28100cdae42a7e28b7f8f47f
Timestamp: 1738871550 Timestamp [UTC]: 2025-02-06 19:52:30 Age [y:d:h:m:s]: 01:093:04:12:44
Block: 1213579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317857 RingCT/type: yes/0
Extra: 010c36e6c71a993269b7362a0730251bfc158d9a6e28100cdae42a7e28b7f8f47f02110000000b27ff1f91000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 59225c176eab5a4a2edac22022a1bd54da6e5a0f36d82ec4d8f1c517167c54a3 0.000600000000 1700358 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": 1213589, "vin": [ { "gen": { "height": 1213579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59225c176eab5a4a2edac22022a1bd54da6e5a0f36d82ec4d8f1c517167c54a3" } } ], "extra": [ 1, 12, 54, 230, 199, 26, 153, 50, 105, 183, 54, 42, 7, 48, 37, 27, 252, 21, 141, 154, 110, 40, 16, 12, 218, 228, 42, 126, 40, 183, 248, 244, 127, 2, 17, 0, 0, 0, 11, 39, 255, 31, 145, 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: