Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2366f2c245b53a873c849fb36aac8396673fe3d0b1021d7c4bb5a9ea669ce8e8

Tx prefix hash: eb2ff5d55b0b263251480abd1de31d920cae8cddc00e9ae3c8690ffc1c038b8b
Tx public key: 610512415f1f5c07c906b26a112c1e4fb8dffd2dc500611bc4c46e966b6a696b
Timestamp: 1706315249 Timestamp [UTC]: 2024-01-27 00:27:29 Age [y:d:h:m:s]: 02:300:00:50:56
Block: 944074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 739420 RingCT/type: yes/0
Extra: 01610512415f1f5c07c906b26a112c1e4fb8dffd2dc500611bc4c46e966b6a696b02110000000659dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ef43371d08bad4608fb719ed493425f6924cab15e45a61db5914f9781ef49be5 0.000600000000 1402300 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": 944084, "vin": [ { "gen": { "height": 944074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef43371d08bad4608fb719ed493425f6924cab15e45a61db5914f9781ef49be5" } } ], "extra": [ 1, 97, 5, 18, 65, 95, 31, 92, 7, 201, 6, 178, 106, 17, 44, 30, 79, 184, 223, 253, 45, 197, 0, 97, 27, 196, 196, 110, 150, 107, 106, 105, 107, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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: