← previous blocknext block →recent activity
Analyzing
Block #86,225,666
18 transactions · 15 stateful · 2026-07-07 16:11:03 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,225,666 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e438da2…5236
0x34b655…2a6f
6 touches
3 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
6 touches
3 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
6 touches
3 conflicts
0x6c0d4c60…31c4
0x34b655…2a6f
4 touches
1 conflict
0x6fc24f20…f3c7
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 0x5e438da2d3…215236
Audit this contract →
← previous block·next block →recent activity