← previous blocknext block →recent activity
Analyzing
Block #97,628,210
21 transactions · 20 stateful · 2026-08-20 12:43:10 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,628,210 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w08w09w110w211w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x16267838…37a0
0x34b655…2a6f
4 touches
1 conflict
0x20821530…e631
0x34b655…2a6f
4 touches
1 conflict
0x3fb8d6f7…6f61
0x34b655…2a6f
4 touches
1 conflict
0x47d2ed5d…9564
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity