← previous blocknext block →recent activity
Analyzing
Block #95,350,600
24 transactions · 20 stateful · 2026-08-12 12:54:29 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,350,600 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w110w211w012w013w114w116w218w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc1d936ef…b7ac
0x34b655…2a6f
8 touches
6 conflicts
0xfc6ee758…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x7523c6af…ea66
0x34b655…2a6f
6 touches
3 conflicts
0x830419d9…fe96
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity