← previous blocknext block →recent activity
Analyzing
Block #90,618,500
14 transactions · 13 stateful · 2026-07-26 23:37:41 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,618,500 · 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
1w02w15w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab4aea39…fcaa
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7485bb0e…d1e0
0x34b655…2a6f
4 touches
1 conflict
0x1e01b4ad…8180
0x34b655…2a6f
2 touches
0 conflicts
0x200674a0…7fe4
0x34b655…2a6f
2 touches
0 conflicts
0x921a58d1…db22
0x34b655…2a6f
2 touches
0 conflicts
0x2d2ac3ab…c1b6
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xab4aea3921…b6fcaa
Audit this contract →
← previous block·next block →recent activity