Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2ccefe7d1e5999a308408ddc8334ab01d21eb65bf71cb6aebc835a198968b63

Tx prefix hash: 45dfca0104e3119c2d8846c713f8d9f8b1b897a70a1ddb8a51fc27df4c591b67
Tx public key: eb5ce82814f50a1326292c85e528ab229f35c028e9b234b94d8d02ca1135bb3f
Timestamp: 1773040326 Timestamp [UTC]: 2026-03-09 07:12:06 Age [y:d:h:m:s]: 00:250:10:28:09
Block: 1493909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184388 RingCT/type: yes/0
Extra: 01eb5ce82814f50a1326292c85e528ab229f35c028e9b234b94d8d02ca1135bb3f021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4ea42c040a101060e41c105f6c5b4e661786be5d6084d468cecc65cf1b9afdf9 0.000600000000 1983475 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": 1493919, "vin": [ { "gen": { "height": 1493909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ea42c040a101060e41c105f6c5b4e661786be5d6084d468cecc65cf1b9afdf9" } } ], "extra": [ 1, 235, 92, 232, 40, 20, 245, 10, 19, 38, 41, 44, 133, 229, 40, 171, 34, 159, 53, 192, 40, 233, 178, 52, 185, 77, 141, 2, 202, 17, 53, 187, 63, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: