← previous blocknext block →recent activity
Analyzing
Block #90,839,167
8 transactions · 7 stateful · 2026-07-27 18:07:55 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,839,167 · 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
2w04w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0c15f714…46ab
0x34b655…2a6f
2 touches
0 conflicts
0x10379e8d…3675
0x34b655…2a6f
2 touches
0 conflicts
0x120c1aaa…8eaf
0x34b655…2a6f
2 touches
0 conflicts
0x159cff26…7665
0x34b655…2a6f
2 touches
0 conflicts
0x3a56380e…e955
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 0x9fd372a13e…ada959
Audit this contract →
← previous block·next block →recent activity