Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d76b87f1ed7c86c5c3d473f030bd5301a705fa84ffd5d1c807a67ffb28b64063

Tx prefix hash: 7f716a75774996c87ee998d5e5af92c519d41ff016cf9764abb76726572a0f87
Tx public key: d3ef2f4c849dc5aa737446724add6fc4e2698d5f99e760c5d0a674ff9c5c5cb8
Timestamp: 1743665978 Timestamp [UTC]: 2025-04-03 07:39:38 Age [y:d:h:m:s]: 01:230:13:32:06
Block: 1253260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428900 RingCT/type: yes/0
Extra: 01d3ef2f4c849dc5aa737446724add6fc4e2698d5f99e760c5d0a674ff9c5c5cb80211000000034060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 18dc38cc84bf4011056d3e1a15b75c9a7df859829b5db47e4c6449fdb1707803 0.000600000000 1740341 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": 1253270, "vin": [ { "gen": { "height": 1253260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18dc38cc84bf4011056d3e1a15b75c9a7df859829b5db47e4c6449fdb1707803" } } ], "extra": [ 1, 211, 239, 47, 76, 132, 157, 197, 170, 115, 116, 70, 114, 74, 221, 111, 196, 226, 105, 141, 95, 153, 231, 96, 197, 208, 166, 116, 255, 156, 92, 92, 184, 2, 17, 0, 0, 0, 3, 64, 96, 246, 210, 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: