← previous blocknext block →recent activity
Analyzing
Block #90,545,603
16 transactions · 15 stateful · 2026-07-26 17:30:58 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
1.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,545,603 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
16 touches
28 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0x4bc1abab…5874
0x34b655…2a6f
12 touches
15 conflicts
0x01257dfc…ce9a
0x34b655…2a6f
9 touches
10 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0x0b7b1a2a…f022
0x34b655…2a6f
5 touches
3 conflicts
0x9d9bed71…d466
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
28 conflicts on slot 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity