← previous blocknext block →recent activity
Analyzing
Block #88,366,257
39 transactions · 35 stateful · 2026-07-17 14:47:11 UTC
Parallelism
72/100
Blocked
66%
Avg conflicts / tx
1.67
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #88,366,257 · 39 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w18w29w310w411w512w013w114w215w320w326w229w431w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb9834665…e363
0x34b655…2a6f
10 touches
10 conflicts
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0xc4de6652…13f4
0x34b655…2a6f
8 touches
6 conflicts
0xa0d3a786…91d9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 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: 0x48cba278…e2b48b
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity