← previous blocknext block →recent activity
Analyzing
Block #97,385,320
26 transactions · 23 stateful · 2026-08-19 16:00:27 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,385,320 · 26 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
1w03w04w15w18w09w113w114w215w216w317w423w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2efe39…1f03
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x482729e0…c3f7
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x1ae67be7…f1aa
0x34b655…2a6f
4 touches
1 conflict
0x610aa855…5ecd
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
3 conflicts on slot 0xac2efe39b0…0e1f03
Audit this contract →
← previous block·next block →recent activity