Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eff1dd3de05c82f8e852fccc5936e44a073384884b335f0b3122f6b841acdb1e

Tx prefix hash: ca7846df0f15abff17c995b7767376ac0149362b737c78675ae32455a686e9ff
Tx public key: 7881873d7e69ae38cb850bca56481ae509fc226a34ae17ae0f57ce62fba80552
Timestamp: 1746156552 Timestamp [UTC]: 2025-05-02 03:29:12 Age [y:d:h:m:s]: 01:017:04:50:32
Block: 1273881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264241 RingCT/type: yes/0
Extra: 017881873d7e69ae38cb850bca56481ae509fc226a34ae17ae0f57ce62fba805520211000000029f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 335b212f0362063c818961678641e7a2e96cc7a104ac6e3eeaff87a08694b01c 0.000600000000 1761168 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": 1273891, "vin": [ { "gen": { "height": 1273881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "335b212f0362063c818961678641e7a2e96cc7a104ac6e3eeaff87a08694b01c" } } ], "extra": [ 1, 120, 129, 135, 61, 126, 105, 174, 56, 203, 133, 11, 202, 86, 72, 26, 229, 9, 252, 34, 106, 52, 174, 23, 174, 15, 87, 206, 98, 251, 168, 5, 82, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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: