← previous blocknext block →recent activity
Analyzing
Block #90,993,702
14 transactions · 13 stateful · 2026-07-28 07:05:32 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,993,702 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w08w19w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62b26c37…87d6
0x34b655…2a6f
6 touches
3 conflicts
0xb46bb9bf…deb7
0x34b655…2a6f
6 touches
3 conflicts
0xb77363ff…ace7
0x34b655…2a6f
6 touches
3 conflicts
0x8b35c69c…3630
0x34b655…2a6f
5 touches
3 conflicts
0x421099c9…8896
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x742436a7…c4d4
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 0x62b26c37ec…fb87d6
Audit this contract →
← previous block·next block →recent activity