Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34780475c85dad5ac28a4b7aa6c8e0950f8fab93fdd6d61b68d9adb39f9d3a8a

Tx prefix hash: 0001b2325110ccd301b5c020842af6a151b32cf184cc63d74cbeaa39df5dd85e
Tx public key: e1916519b53a93dc49aafb38c9541e1a15421a87099a45f8a4c5dfcfa093e58a
Timestamp: 1774859038 Timestamp [UTC]: 2026-03-30 08:23:58 Age [y:d:h:m:s]: 00:233:17:19:27
Block: 1508959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172581 RingCT/type: yes/0
Extra: 01e1916519b53a93dc49aafb38c9541e1a15421a87099a45f8a4c5dfcfa093e58a021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7582af91e8a65d75c5be8e3fb64372c4e0c8f0983585c21854fa0cedb3571d36 0.000600000000 1998713 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": 1508969, "vin": [ { "gen": { "height": 1508959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7582af91e8a65d75c5be8e3fb64372c4e0c8f0983585c21854fa0cedb3571d36" } } ], "extra": [ 1, 225, 145, 101, 25, 181, 58, 147, 220, 73, 170, 251, 56, 201, 84, 30, 26, 21, 66, 26, 135, 9, 154, 69, 248, 164, 197, 223, 207, 160, 147, 229, 138, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: