← previous blocknext block →recent activity
Analyzing
Block #91,957,801
16 transactions · 15 stateful · 2026-07-31 15:58:41 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,957,801 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w410w013w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9da46f45…611d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xe5a9274d…78d7
0x34b655…2a6f
10 touches
10 conflicts
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
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
10 conflicts on slot 0x9da46f4505…f5611d
Audit this contract →
← previous block·next block →recent activity