Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 936204f7b23752b7dc0565adb64d299074d17f7b7ca5617cda418324f72cea3a

Tx prefix hash: 7c98de74db8e4d55456404998e33ed19c52e2ed81e94f77d1659a9248242ca09
Tx public key: 12bffd3f78a258212e2416fa19a3a4e61a30c2acbb7a12b1a4b3d813842625d4
Timestamp: 1709183549 Timestamp [UTC]: 2024-02-29 05:12:29 Age [y:d:h:m:s]: 02:266:08:06:07
Block: 967889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 715541 RingCT/type: yes/0
Extra: 0112bffd3f78a258212e2416fa19a3a4e61a30c2acbb7a12b1a4b3d813842625d40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4649be32e45ee446b4b11049fa0f3498d20926c370a95720e5dafe82f1a96ce0 0.000600000000 1427682 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": 967899, "vin": [ { "gen": { "height": 967889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4649be32e45ee446b4b11049fa0f3498d20926c370a95720e5dafe82f1a96ce0" } } ], "extra": [ 1, 18, 191, 253, 63, 120, 162, 88, 33, 46, 36, 22, 250, 25, 163, 164, 230, 26, 48, 194, 172, 187, 122, 18, 177, 164, 179, 216, 19, 132, 38, 37, 212, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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: