← previous blocknext block →recent activity
Analyzing
Block #90,786,140
32 transactions · 25 stateful · 2026-07-27 13:41:01 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,786,140 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w18w215w122w026w127w228w329w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x0dd44476…ef40
0x34b655…2a6f
6 touches
3 conflicts
0x255ba9f3…396d
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x91803cbc…2f15
0x34b655…2a6f
4 touches
1 conflict
0x94b46bd0…e95d
0x34b655…2a6f
4 touches
1 conflict
0x96bff3d7…a95a
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity