← previous blocknext block →recent activity
Analyzing
Block #90,791,665
17 transactions · 15 stateful · 2026-07-27 14:08:51 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #90,791,665 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w210w311w412w514w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x176cc2f5…6fad
0x34b655…2a6f
8 touches
6 conflicts
0x379dc435…6616
0x34b655…2a6f
6 touches
3 conflicts
0x2dae10bc…18be
0x34b655…2a6f
6 touches
3 conflicts
0x9375a764…dca1
0x34b655…2a6f
6 touches
3 conflicts
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity