← previous blocknext block →recent activity
Analyzing
Block #90,784,112
26 transactions · 20 stateful · 2026-07-27 13:30:49 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,784,112 · 26 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
1w02w13w011w212w213w014w115w116w217w221w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8326b13b…bac0
0x34b655…2a6f
6 touches
3 conflicts
0x05e83dc2…b7a0
0x34b655…2a6f
4 touches
1 conflict
0x146c718c…8a22
0x34b655…2a6f
4 touches
1 conflict
0x42e08579…09bb
0x34b655…2a6f
4 touches
1 conflict
0x53bda555…3810
0x34b655…2a6f
4 touches
1 conflict
0x7032dc14…49ea
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