← previous blocknext block →recent activity
Analyzing
Block #90,221,204
12 transactions · 9 stateful · 2026-07-25 14:04:00 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #90,221,204 · 12 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x998eda6e…d572
0x34b655…2a6f
4 touches
1 conflict
0xc4dc32ca…83f9
0x34b655…2a6f
4 touches
1 conflict
0xc4dc32ca…83fa
0x34b655…2a6f
4 touches
1 conflict
0xd1d77a12…4b8e
0x34b655…2a6f
4 touches
1 conflict
0xdb8897f4…d365
0x34b655…2a6f
4 touches
1 conflict
0x87292c3e…5e25
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
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 0x998eda6e86…fcd572
Audit this contract →
← previous block·next block →recent activity