← previous blocknext block →recent activity
Analyzing
Block #86,511,936
16 transactions · 14 stateful · 2026-07-09 00:03:20 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,511,936 · 16 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
2w013w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x000aa119…0cb2
0x34b655…2a6f
2 touches
0 conflicts
0x0cd78001…c8bc
0x34b655…2a6f
2 touches
0 conflicts
0x322dcd34…8718
0x34b655…2a6f
2 touches
0 conflicts
0x32f1fe90…5ee3
0x34b655…2a6f
2 touches
0 conflicts
0x342f88f5…2a06
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 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity