← previous blocknext block →recent activity
Analyzing
Block #90,559,418
7 transactions · 7 stateful · 2026-07-26 18:40:28 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,559,418 · 7 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6cece75…ea3a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf273c816…7560
0x34b655…2a6f
4 touches
1 conflict
0xf273c816…7561
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x1294a92c…f91e
0x34b655…2a6f
2 touches
0 conflicts
0x4253010a…4700
0x34b655…2a6f
2 touches
0 conflicts
0x445e3640…c420
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 0xc6cece7517…95ea3a
Audit this contract →
← previous block·next block →recent activity