← previous blocknext block →recent activity
Analyzing
Block #91,821,713
11 transactions · 10 stateful · 2026-07-31 04:34:00 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,821,713 · 11 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
2w03w05w16w28w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d781581…d688
0x34b655…2a6f
8 touches
6 conflicts
0xb1b58b33…874f
0x34b655…2a6f
8 touches
6 conflicts
0xfe97c123…af37
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x2b781209…93f1
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x695d89bf…2cb7
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 0x2d78158123…36d688
Audit this contract →
← previous block·next block →recent activity