← previous blocknext block →recent activity
Analyzing
Block #90,769,745
23 transactions · 19 stateful · 2026-07-27 12:18:32 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,769,745 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w07w08w19w210w011w115w016w117w218w319w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0xfbe161dd…757b
0x3bd359…433a
6 touches
3 conflicts
0xedf7bb0d…5fde
0x065c9d…c394
5 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x0b34a794…400b
0x34b655…2a6f
4 touches
1 conflict
0x10797f0b…439a
0x34b655…2a6f
4 touches
1 conflict
0x2a296f2d…2630
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
3 conflicts on slot 0xf2f4727df6…a5cdb7
Audit this contract →
← previous block·next block →recent activity