Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffdf4451ec686fa65ea84bbdf2c10407625cada09ef19f8253d39492518cbc09

Tx prefix hash: 3cf3e42dffef49e0dc053a64d9e30024546f2c898d93b86bb440e2c7ce7745e4
Tx public key: 84701c81a5a473a032c17efae25758672a2b0ea387eb38ea00660dbe1eb0c4db
Timestamp: 1717320090 Timestamp [UTC]: 2024-06-02 09:21:30 Age [y:d:h:m:s]: 02:091:02:10:54
Block: 1035351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590443 RingCT/type: yes/0
Extra: 0184701c81a5a473a032c17efae25758672a2b0ea387eb38ea00660dbe1eb0c4db02110000000759dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3345e5451f2e8b3f12c9a3e5b90dce5909bd043accb4722d5328ba63df4b7237 0.000600000000 1503872 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": 1035361, "vin": [ { "gen": { "height": 1035351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3345e5451f2e8b3f12c9a3e5b90dce5909bd043accb4722d5328ba63df4b7237" } } ], "extra": [ 1, 132, 112, 28, 129, 165, 164, 115, 160, 50, 193, 126, 250, 226, 87, 88, 103, 42, 43, 14, 163, 135, 235, 56, 234, 0, 102, 13, 190, 30, 176, 196, 219, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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: