← previous blocknext block →recent activity
Analyzing
Block #90,866,384
16 transactions · 16 stateful · 2026-07-27 20:24:52 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,866,384 · 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
3w04w05w16w27w18w29w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92faf088…12e4
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x74f95963…01a2
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0x755b0df4…f57e
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
10 conflicts on slot 0x92faf088f7…9b12e4
Audit this contract →
← previous block·next block →recent activity