← previous blocknext block →recent activity
Analyzing
Block #97,196,131
10 transactions · 10 stateful · 2026-08-18 23:54:23 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,196,131 · 10 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
2w03w14w25w36w47w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
6 touches
3 conflicts
0xd8153d80…7823
0xa6afd3…d132
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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: Wrapped Ether (WETH)
10 conflicts on slot 0x11b69a7ea1…83334e
Audit this contract →
← previous block·next block →recent activity