← previous blocknext block →recent activity
Analyzing
Block #86,752,941
17 transactions · 14 stateful · 2026-07-10 02:56:30 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,752,941 · 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
1w02w14w05w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a6290da…e683
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1b72707f…a306
0x34b655…2a6f
4 touches
1 conflict
0x4b6fb1f8…f5d9
0x40c49f…2af0
2 touches
0 conflicts
0x90c416f3…0012
0x40c49f…2af0
2 touches
0 conflicts
0xc579d48d…6b05
0x40c49f…2af0
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 0x3a6290da4d…93e683
Audit this contract →
← previous block·next block →recent activity