← previous blocknext block →recent activity
Analyzing
Block #90,706,725
12 transactions · 9 stateful · 2026-07-27 07:01:31 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,706,725 · 12 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
4w05w16w27w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d040d9…9ae3
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x27034002…2f27
0x34b655…2a6f
4 touches
1 conflict
0x2127ebd5…7b99
0x34b655…2a6f
4 touches
1 conflict
0xa5ab7b8a…c97b
0x34b655…2a6f
2 touches
0 conflicts
0xb1b21ea8…d790
0x34b655…2a6f
2 touches
0 conflicts
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 0xd6d040d989…9c9ae3
Audit this contract →
← previous block·next block →recent activity