← previous blocknext block →recent activity
Analyzing
Block #97,558,432
26 transactions · 26 stateful · 2026-08-20 06:50:00 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,558,432 · 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
2w05w07w08w09w110w111w212w313w314w415w421w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x75fe24d2…46f9
0x34b655…2a6f
6 touches
3 conflicts
0x728f999a…832f
0x34b655…2a6f
4 touches
1 conflict
0x57265ecc…70a7
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x275ce6ab…730a
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
6 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity