← previous blocknext block →recent activity
Analyzing
Block #90,463,043
10 transactions · 7 stateful · 2026-07-26 10:35:38 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,463,043 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3a5784b…1b60
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd7d3cccb…fd18
0x34b655…2a6f
4 touches
1 conflict
0xf8a748aa…446a
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x434010de…83fe
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
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 0xf3a5784b65…671b60
Audit this contract →
← previous block·next block →recent activity