← previous blocknext block →recent activity
Analyzing
Block #90,822,150
19 transactions · 18 stateful · 2026-07-27 16:42:19 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,822,150 · 19 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
1w02w04w05w16w17w28w310w412w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4228eb58…8905
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x449d101e…ea3f
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x4228eb5822…7a8905
Audit this contract →
← previous block·next block →recent activity