← previous blocknext block →recent activity
Analyzing
Block #90,975,900
13 transactions · 13 stateful · 2026-07-28 05:35:46 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,975,900 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe870e232…7369
0xf9b0c8…8081
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x39fb42f2…35f2
0x34b655…2a6f
4 touches
1 conflict
0x89db0485…8c3b
0x34b655…2a6f
4 touches
1 conflict
0xc85f42b6…6f23
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8488f10f…9353
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9354
0x2b46c0…1669
2 touches
0 conflicts
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: 0xf9b0c8ee…ea8081
1 conflict on slot 0xe870e2326a…1a7369
Audit this contract →
← previous block·next block →recent activity