← previous blocknext block →recent activity
Analyzing
Block #90,499,901
17 transactions · 17 stateful · 2026-07-26 13:41:06 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,499,901 · 17 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
1w02w03w14w25w36w48w110w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0561ada0…ff23
0x34b655…2a6f
10 touches
10 conflicts
0x58e9c5c4…c2a1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x83022250…86f3
0x34b655…2a6f
6 touches
3 conflicts
0x8a4ab7ad…876a
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
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
10 conflicts on slot 0x0561ada01f…04ff23
Audit this contract →
← previous block·next block →recent activity