← previous blocknext block →recent activity
Analyzing
Block #90,770,435
14 transactions · 14 stateful · 2026-07-27 12:22:00 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,770,435 · 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
2w03w16w18w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x358d6b84…2f88
0x34b655…2a6f
6 touches
3 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0xde9d38a8…4c0f
0x34b655…2a6f
4 touches
1 conflict
0xe1a9f808…b867
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x181ad9cf…26f4
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
3 conflicts on slot 0x358d6b84a1…b42f88
Audit this contract →
← previous block·next block →recent activity