← previous blocknext block →recent activity
Analyzing
Block #97,384,890
21 transactions · 19 stateful · 2026-08-19 15:57:17 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,384,890 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w310w211w412w513w014w616w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x967ba723…6d0f
0x34b655…2a6f
8 touches
6 conflicts
0xbfe333a4…687f
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x3aee421b…c4ba
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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 0x967ba7239d…2d6d0f
Audit this contract →
← previous block·next block →recent activity