Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64b949a56235cb9fc8276c1b17c4e6e8d4fd0fd27318a8d98ff16f3e86a1cdd4

Tx prefix hash: f4b61961a2b3c3e710bda8aa420dff81e55f21ad6a2b39a118075af0e870a5e8
Tx public key: 6fe1db8953913a2929ec69ec95d64621c6769e4fae48b793abcc59292ff97a4a
Timestamp: 1770141400 Timestamp [UTC]: 2026-02-03 17:56:40 Age [y:d:h:m:s]: 00:284:07:04:09
Block: 1469947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208577 RingCT/type: yes/0
Extra: 016fe1db8953913a2929ec69ec95d64621c6769e4fae48b793abcc59292ff97a4a02110000000bf188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6d6f1e6fc13338ab9432cffa22a32d502b2f223738f8d643a6dc35ecee01d18c 0.000600000000 1959213 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": 1469957, "vin": [ { "gen": { "height": 1469947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d6f1e6fc13338ab9432cffa22a32d502b2f223738f8d643a6dc35ecee01d18c" } } ], "extra": [ 1, 111, 225, 219, 137, 83, 145, 58, 41, 41, 236, 105, 236, 149, 214, 70, 33, 198, 118, 158, 79, 174, 72, 183, 147, 171, 204, 89, 41, 47, 249, 122, 74, 2, 17, 0, 0, 0, 11, 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: