← previous blocknext block →recent activity
Analyzing
Block #86,226,829
13 transactions · 10 stateful · 2026-07-07 16:18:48 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,226,829 · 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
2w04w05w16w17w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xddd20e39…d524
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x8418fd37…69f7
0xd32edf…ff58
3 touches
1 conflict
0x066323da…7fc6
0x34b655…2a6f
2 touches
0 conflicts
0x11f9e5cc…fafb
0x34b655…2a6f
2 touches
0 conflicts
0x1b1b086a…4542
0x34b655…2a6f
2 touches
0 conflicts
0x218b4efb…a93a
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 0xddd20e3989…a2d524
Audit this contract →
← previous block·next block →recent activity