← previous blocknext block →recent activity
Analyzing
Block #86,154,911
17 transactions · 16 stateful · 2026-07-07 08:18:40 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,154,911 · 17 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
1w02w13w24w05w06w110w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x33910f6c…a606
0xd32edf…ff58
5 touches
3 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
4 touches
1 conflict
0x4d658fb7…ed44
0x34b655…2a6f
4 touches
1 conflict
0xa14c51c5…1146
0x34b655…2a6f
4 touches
1 conflict
0xb5c2065a…2ca3
0x34b655…2a6f
4 touches
1 conflict
0xde398ff4…00ca
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity