← previous blocknext block →recent activity
Analyzing
Block #97,356,105
16 transactions · 16 stateful · 2026-08-19 13:26:34 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,356,105 · 16 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
2w03w14w26w310w411w512w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8218911e…3bed
0x34b655…2a6f
8 touches
6 conflicts
0xb1dd4ba4…6937
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0x0b2ae7be…fede
0x34b655…2a6f
4 touches
1 conflict
0xed19fb96…2166
0x34b655…2a6f
4 touches
1 conflict
0x96ed2d2d…2690
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity