← previous blocknext block →recent activity
Analyzing
Block #91,957,424
9 transactions · 8 stateful · 2026-07-31 15:56:47 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,957,424 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ea5c5d8…6813
0x34b655…2a6f
4 touches
1 conflict
0x9ea5c5d8…6814
0x34b655…2a6f
4 touches
1 conflict
0x4f41aff2…ea0a
0x34b655…2a6f
4 touches
1 conflict
0x1294a92c…f91e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe9ac01c2…66c1
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
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 0x9ea5c5d836…4d6813
Audit this contract →
← previous block·next block →recent activity