← previous blocknext block →recent activity
Analyzing
Block #90,706,965
14 transactions · 14 stateful · 2026-07-27 07:02:44 UTC
Parallelism
64/100
Blocked
29%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,706,965 · 14 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
4w06w18w29w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd800e635…b1d7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
6 touches
3 conflicts
0x59e54d3e…4c85
0x34b655…2a6f
6 touches
3 conflicts
0x505b37d8…d3fc
0x34b655…2a6f
4 touches
1 conflict
0x3d4c0233…20a5
0x34b655…2a6f
4 touches
1 conflict
0x709cb1f7…ed38
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity