← previous blocknext block →recent activity
Analyzing
Block #90,544,637
8 transactions · 7 stateful · 2026-07-26 17:26:07 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,544,637 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecf72a3c…67a3
0x34b655…2a6f
4 touches
1 conflict
0x605f05fa…4ebc
0x34b655…2a6f
4 touches
1 conflict
0x9f889f59…5c45
0x34b655…2a6f
4 touches
1 conflict
0x6561b826…f343
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x06c2c8c1…c2a8
0x34b655…2a6f
2 touches
0 conflicts
0x06c2c8c1…c2a9
0x34b655…2a6f
2 touches
0 conflicts
0x1e737223…2278
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 0xecf72a3cf0…7b67a3
Audit this contract →
← previous block·next block →recent activity