← previous blocknext block →recent activity
Analyzing
Block #90,719,153
10 transactions · 10 stateful · 2026-07-27 08:04:03 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,719,153 · 10 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
1w03w06w17w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeeb1a876…28d3
0x34b655…2a6f
4 touches
1 conflict
0xfb24441a…4183
0x34b655…2a6f
4 touches
1 conflict
0x5a3a03c4…e559
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x3fcc24d4…fa74
0x851145…3f07
4 touches
1 conflict
0x6b76d7a1…d19b
0x851145…3f07
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7a12283f…b18a
0x2b46c0…1669
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 0xeeb1a876d1…6628d3
Audit this contract →
← previous block·next block →recent activity