Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 785f6ec6efb365e915b7fc9585a1520da359bef4b4ccdcb2a5a9fc3173a72dfc

Tx prefix hash: df3f4d6921924abc47e83354705a4a9a42054dc269f289db154cbed0bc675716
Tx public key: f262847a2b5b06baf0a4c55c08c78136deea5f80144dca1b8ab5a17aa53ba42f
Timestamp: 1774980190 Timestamp [UTC]: 2026-03-31 18:03:10 Age [y:d:h:m:s]: 00:231:12:57:19
Block: 1509955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171002 RingCT/type: yes/0
Extra: 01f262847a2b5b06baf0a4c55c08c78136deea5f80144dca1b8ab5a17aa53ba42f021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8d9cd34e8d7011c691571a498679b8a9351ca82414607a3af83b8d53177bb6e8 0.000600000000 1999731 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": 1509965, "vin": [ { "gen": { "height": 1509955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d9cd34e8d7011c691571a498679b8a9351ca82414607a3af83b8d53177bb6e8" } } ], "extra": [ 1, 242, 98, 132, 122, 43, 91, 6, 186, 240, 164, 197, 92, 8, 199, 129, 54, 222, 234, 95, 128, 20, 77, 202, 27, 138, 181, 161, 122, 165, 59, 164, 47, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: