← previous blocknext block →recent activity
Analyzing
Block #90,892,460
16 transactions · 16 stateful · 2026-07-27 22:36:02 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,892,460 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w27w311w412w513w615w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xa279b18d…63bc
0x34b655…2a6f
10 touches
10 conflicts
0x7907f7f7…dc3f
0x34b655…2a6f
6 touches
3 conflicts
0x2d443697…48c7
0x34b655…2a6f
6 touches
3 conflicts
0xeb0b1d43…9559
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x9579025c…c3ec
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity