← previous blocknext block →recent activity
Analyzing
Block #90,978,554
14 transactions · 13 stateful · 2026-07-28 05:49:07 UTC
Parallelism
43/100
Blocked
54%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,978,554 · 14 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
4w05w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x705ab4ae…0162
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0x8641bdc9…7e57
0x34b655…2a6f
8 touches
6 conflicts
0x8235dfbf…0db0
0x34b655…2a6f
5 touches
3 conflicts
0x5ca6ebb9…3142
0x34b655…2a6f
4 touches
1 conflict
0xa57da2e8…e811
0x34b655…2a6f
3 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity