← previous blocknext block →recent activity
Analyzing
Block #91,431,976
14 transactions · 14 stateful · 2026-07-29 19:53:24 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,431,976 · 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
3w04w16w08w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe498a85…9dc4
0x34b655…2a6f
4 touches
1 conflict
0xeafd66de…0faf
0x34b655…2a6f
4 touches
1 conflict
0xfcc19724…4e34
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x25f10f57…72de
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x5d494c83…a65e
0x34b655…2a6f
4 touches
1 conflict
0x6aedfcab…3dfd
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
1 conflict on slot 0xfe498a8552…b49dc4
Audit this contract →
← previous block·next block →recent activity