← previous blocknext block →recent activity
Analyzing
Block #90,918,882
13 transactions · 12 stateful · 2026-07-28 00:48:58 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,918,882 · 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
2w03w14w25w36w07w18w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x89f9a9c7…7b63
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0x21c9fd73…dae4
0x34b655…2a6f
4 touches
1 conflict
0x2fade833…5de4
0x34b655…2a6f
4 touches
1 conflict
0x3accd47f…d16e
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity