← previous blocknext block →recent activity
Analyzing
Block #97,613,214
17 transactions · 15 stateful · 2026-08-20 11:27:43 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,613,214 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w07w010w011w112w113w114w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17f192de…765e
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x68cb5388…191a
0x34b655…2a6f
4 touches
1 conflict
0xb2560305…f27d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
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
3 conflicts on slot 0x17f192de5b…37765e
Audit this contract →
← previous block·next block →recent activity