← previous blocknext block →recent activity
Analyzing
Block #90,867,446
12 transactions · 12 stateful · 2026-07-27 20:30:13 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,867,446 · 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
2w03w14w05w16w28w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c5238c6…f2dc
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x0f7df08f…cad4
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3dc8ed8f…9df1
0x34b655…2a6f
4 touches
1 conflict
0x3dcf4944…078c
0x34b655…2a6f
4 touches
1 conflict
0x3deaf71f…c229
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
6 conflicts on slot 0x5c5238c656…aaf2dc
Audit this contract →
← previous block·next block →recent activity