← previous blocknext block →recent activity
Analyzing
Block #90,884,342
13 transactions · 13 stateful · 2026-07-27 21:55:12 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,884,342 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w112w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6250be1b…f951
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x69a45f39…39aa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x2c3dbd78…1a68
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 0x6250be1b47…15f951
Audit this contract →
← previous block·next block →recent activity