← previous blocknext block →recent activity
Analyzing
Block #97,611,692
19 transactions · 18 stateful · 2026-08-20 11:20:04 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,611,692 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w110w211w312w413w514w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x2e5cdd04…22ab
0x34b655…2a6f
8 touches
6 conflicts
0x3b3a5945…10d0
0x34b655…2a6f
6 touches
3 conflicts
0xed9f23a7…1129
0x34b655…2a6f
6 touches
3 conflicts
0xedad6e9b…3425
0x34b655…2a6f
4 touches
1 conflict
0x87a380d9…2d04
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
6 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity