← previous blocknext block →recent activity
Analyzing
Block #86,686,931
22 transactions · 20 stateful · 2026-07-09 19:35:36 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,686,931 · 22 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
1w02w13w04w15w27w28w19w312w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa08f40b2…9a93
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x546671c8…080a
0x34b655…2a6f
6 touches
3 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0x6f900be0…cd6e
0x34b655…2a6f
4 touches
1 conflict
0x74fce6ad…7895
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xa08f40b255…099a93
Audit this contract →
← previous block·next block →recent activity