← previous blocknext block →recent activity
Analyzing
Block #86,774,422
12 transactions · 11 stateful · 2026-07-10 05:19:58 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,774,422 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7fe04a…3c56
0x34b655…2a6f
4 touches
1 conflict
0x4c2e78a1…2f95
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2186e6b9…1235
0x065c9d…c394
2 touches
0 conflicts
0x61d4f193…9de1
0x065c9d…c394
2 touches
0 conflicts
0x05e1eba1…6491
0x34b655…2a6f
2 touches
0 conflicts
0x315e07b8…9823
0x34b655…2a6f
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
1 conflict on slot 0xec7fe04ad1…2d3c56
Audit this contract →
← previous block·next block →recent activity