← previous blocknext block →recent activity
Analyzing
Block #88,343,890
21 transactions · 17 stateful · 2026-07-17 12:16:36 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,343,890 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w07w110w111w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc9dce17a…a1a1
0x34b655…2a6f
8 touches
6 conflicts
0x8252706a…7ca5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x6b11b9de…f60a
0x34b655…2a6f
4 touches
1 conflict
0x5cc477b5…1cf3
0x34b655…2a6f
4 touches
1 conflict
0x65b64b8a…13c7
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity