← previous blocknext block →recent activity
Analyzing
Block #90,876,108
16 transactions · 15 stateful · 2026-07-27 21:13:47 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #90,876,108 · 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
2w03w14w26w27w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x705ab4ae…0162
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3cb4b659…f735
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xfcbabd3f…86b0
0x34b655…2a6f
5 touches
3 conflicts
0x3ac4916f…73d0
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity