← previous blocknext block →recent activity
Analyzing
Block #97,397,344
22 transactions · 22 stateful · 2026-08-19 17:16:42 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,397,344 · 22 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
1w03w04w05w16w07w28w110w311w413w114w215w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd042b223…f61c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd7a3d42d…e766
0x40c49f…2af0
6 touches
3 conflicts
0x40888ce5…15a6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x3f43e41b…19b5
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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 0xd042b223d5…31f61c
Audit this contract →
← previous block·next block →recent activity