← previous blocknext block →recent activity
Analyzing
Block #91,109,192
20 transactions · 20 stateful · 2026-07-28 16:47:17 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,109,192 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w07w18w19w210w313w414w317w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
6 touches
3 conflicts
0xb37a516b…7822
0x34b655…2a6f
6 touches
3 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x2d93aa7c…07b9
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xcc58c80b6c…80ff79
Audit this contract →
← previous block·next block →recent activity