← previous blocknext block →recent activity
Analyzing
Block #97,567,856
28 transactions · 26 stateful · 2026-08-20 07:38:07 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,567,856 · 28 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
3w04w05w16w28w311w012w113w217w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb094dfef…f562
0x34b655…2a6f
8 touches
6 conflicts
0xea1d91a3…b583
0x34b655…2a6f
8 touches
6 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xb0c4c43b…3d2a
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xb094dfef8b…f5f562
Audit this contract →
← previous block·next block →recent activity