← previous blocknext block →recent activity
Analyzing
Block #86,903,949
11 transactions · 7 stateful · 2026-07-10 19:45:48 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,903,949 · 11 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
3w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe8aac6e…6595
0x34b655…2a6f
4 touches
1 conflict
0x730a64b9…1b00
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8dfef5ae…9361
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xfe8aac6e…6594
0x34b655…2a6f
4 touches
1 conflict
0x57e783c1…f03d
0x34b655…2a6f
2 touches
0 conflicts
0x64d353bf…54eb
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 0xfe8aac6e98…856595
Audit this contract →
← previous block·next block →recent activity