← previous blocknext block →recent activity
Analyzing
Block #91,796,632
18 transactions · 17 stateful · 2026-07-31 02:27:50 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,796,632 · 18 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
1w02w13w04w15w07w110w011w112w215w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1b58b33…874f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x17e67eba…8003
0x34b655…2a6f
4 touches
1 conflict
0x1ed93f99…9f39
0x34b655…2a6f
4 touches
1 conflict
0x37b7341b…4ec9
0x34b655…2a6f
4 touches
1 conflict
0x40442d27…fafc
0x34b655…2a6f
4 touches
1 conflict
0x4b67fb18…a176
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 0xb1b58b3385…e4874f
Audit this contract →
← previous block·next block →recent activity