← previous blocknext block →recent activity
Analyzing
Block #90,879,466
16 transactions · 15 stateful · 2026-07-27 21:30:40 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,879,466 · 16 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
1w03w04w16w17w28w39w411w414w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x69a45f39…39aa
0x34b655…2a6f
8 touches
6 conflicts
0x19ebfd29…e80e
0x34b655…2a6f
8 touches
6 conflicts
0x701208a7…46b3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x796b78ec…83ef
0x34b655…2a6f
4 touches
1 conflict
0xa9660e2b…64df
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity