← previous blocknext block →recent activity
Analyzing
Block #86,300,091
14 transactions · 12 stateful · 2026-07-08 00:27:54 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,300,091 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08d66073…e706
0x34b655…2a6f
6 touches
3 conflicts
0x27dd8ebd…6d57
0x34b655…2a6f
4 touches
1 conflict
0x3f39275f…fc4e
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0x88f36c84…929d
0x34b655…2a6f
2 touches
0 conflicts
0xb03ccb40…ede4
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
3 conflicts on slot 0x08d6607389…0fe706
Audit this contract →
← previous block·next block →recent activity