← previous blocknext block →recent activity
Analyzing
Block #90,785,232
32 transactions · 29 stateful · 2026-07-27 13:36:27 UTC
Parallelism
81/100
Blocked
34%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,785,232 · 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
6w07w18w29w010w015w118w222w325w126w228w329w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
8 touches
6 conflicts
0x9aa1ca79…d902
0x34b655…2a6f
6 touches
3 conflicts
0xfa42bdbe…f9f1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x55641435…4bb9
0x34b655…2a6f
4 touches
1 conflict
0x6aa0302c…bc76
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