← previous blocknext block →recent activity
Analyzing
Block #95,114,091
13 transactions · 13 stateful · 2026-08-11 16:53:42 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,114,091 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w08w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5df7cf2b…bbe5
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x85bfd0af…ce96
0x34b655…2a6f
4 touches
1 conflict
0xf8a748aa…446a
0x34b655…2a6f
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 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
3 conflicts on slot 0x5df7cf2bfe…17bbe5
Audit this contract →
← previous block·next block →recent activity