← previous blocknext block →recent activity
Analyzing
Block #97,358,364
21 transactions · 20 stateful · 2026-08-19 13:38:15 UTC
Parallelism
62/100
Blocked
55%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,358,364 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w36w47w58w613w014w116w517w720w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69a45f39…39aa
0x34b655…2a6f
10 touches
10 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
6 touches
3 conflicts
0x2ce5d13f…f8a9
0x851145…3f07
4 touches
1 conflict
0x2c3dbd78…1a68
0x34b655…2a6f
4 touches
1 conflict
0xa5a114ce…40e2
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 0x69a45f39d6…c739aa
Audit this contract →
← previous block·next block →recent activity