← previous blocknext block →recent activity
Analyzing
Block #90,722,804
16 transactions · 16 stateful · 2026-07-27 08:22:25 UTC
Parallelism
63/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,722,804 · 16 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
1w04w15w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x110a671c…e284
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3230413b…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x529ac99f…e82e
0x34b655…2a6f
4 touches
1 conflict
0x56c1eb47…65a2
0x34b655…2a6f
4 touches
1 conflict
0x66e2720b…f019
0x34b655…2a6f
4 touches
1 conflict
0x70f319b1…ba5f
0x34b655…2a6f
4 touches
1 conflict
0x76f0c3e8…1157
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
3 conflicts on slot 0x110a671c45…0be284
Audit this contract →
← previous block·next block →recent activity