← previous blocknext block →recent activity
Analyzing
Block #86,813,526
19 transactions · 18 stateful · 2026-07-10 09:41:03 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,813,526 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w310w411w515w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x725c0153…5f97
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x63b15849…80b2
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x74355ed1…eda6
0x34b655…2a6f
8 touches
6 conflicts
0x9f40a209…1193
0x34b655…2a6f
8 touches
6 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x725c0153c8…315f97
Audit this contract →
← previous block·next block →recent activity