← previous blocknext block →recent activity
Analyzing
Block #97,554,110
80 transactions · 80 stateful · 2026-08-20 06:28:02 UTC
Parallelism
96/100
Blocked
13%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,554,110 · 80 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w17w08w19w110w212w013w114w116w278w279w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cfec795…7c0e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x8902ba1f…f4b6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6676e4f3…6a9e
0x851145…3f07
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 0x5cfec7957f…867c0e
Audit this contract →
← previous block·next block →recent activity