← previous blocknext block →recent activity
Analyzing
Block #86,243,188
13 transactions · 10 stateful · 2026-07-07 18:08:04 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,243,188 · 13 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
4w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf357ed8b…e65c
0x34b655…2a6f
6 touches
3 conflicts
0x66a0f0ab…3fcf
0x34b655…2a6f
6 touches
3 conflicts
0x5dd1f5d4…deac
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x667658e1…e172
0x34b655…2a6f
4 touches
1 conflict
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0x714b6a6b…d742
0x34b655…2a6f
4 touches
1 conflict
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 0xf357ed8b79…38e65c
Audit this contract →
← previous block·next block →recent activity