← previous blocknext block →recent activity
Analyzing
Block #91,969,017
10 transactions · 8 stateful · 2026-07-31 16:55:05 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,969,017 · 10 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
1w04w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ea5c5d8…6814
0x34b655…2a6f
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0x0a278da2…7b54
0x34b655…2a6f
2 touches
0 conflicts
0x0b05d77e…6f90
0x34b655…2a6f
2 touches
0 conflicts
0x0ec9e741…0f70
0x34b655…2a6f
2 touches
0 conflicts
0x14420c60…fe43
0x34b655…2a6f
2 touches
0 conflicts
0x28f324ed…9db7
0x34b655…2a6f
2 touches
0 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
2 touches
0 conflicts
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…4d6814
Audit this contract →
← previous block·next block →recent activity