← previous blocknext block →recent activity
Analyzing
Block #90,962,448
21 transactions · 19 stateful · 2026-07-28 04:28:05 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,962,448 · 21 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
3w08w19w214w215w016w117w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x41fc2b04…2805
0x34b655…2a6f
4 touches
1 conflict
0x70477692…11bf
0x34b655…2a6f
4 touches
1 conflict
0x91ac91ec…eea0
0x34b655…2a6f
4 touches
1 conflict
0x923c9dce…e69a
0x34b655…2a6f
4 touches
1 conflict
0xb020f356…e558
0x34b655…2a6f
4 touches
1 conflict
0xb2fa1675…4e07
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity