← previous blocknext block →recent activity
Analyzing
Block #86,225,717
14 transactions · 14 stateful · 2026-07-07 16:11:24 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,225,717 · 14 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e438da2…5236
0x34b655…2a6f
4 touches
1 conflict
0x16ca898b…f2b0
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x3b9bb58c…e73a
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x3e033d91…5255
0x34b655…2a6f
2 touches
0 conflicts
0x5d1ac445…5233
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 0x5e438da2d3…215236
Audit this contract →
← previous block·next block →recent activity