← previous blocknext block →recent activity
Analyzing
Block #91,444,892
14 transactions · 14 stateful · 2026-07-29 20:58:22 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,444,892 · 14 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
4w05w16w07w08w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x008d344a…3196
0x34b655…2a6f
6 touches
3 conflicts
0x08a39015…efa0
0x34b655…2a6f
6 touches
3 conflicts
0x585527c4…0924
0x34b655…2a6f
6 touches
3 conflicts
0xb9420325…bb52
0x34b655…2a6f
6 touches
3 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
6 touches
3 conflicts
0x20067ecb…0e41
0x34b655…2a6f
4 touches
1 conflict
0x35725dab…9f7b
0x34b655…2a6f
4 touches
1 conflict
0x3d8fdad4…5bc6
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 0x008d344ad0…cd3196
Audit this contract →
← previous block·next block →recent activity