← previous blocknext block →recent activity
Analyzing
Block #97,467,338
24 transactions · 24 stateful · 2026-08-19 23:10:36 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,467,338 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w19w110w211w212w313w414w515w016w117w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x806c6904…3d63
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x18865c9d…8ced
0xa6afd3…d132
4 touches
1 conflict
0xb97c885b…2933
0x34b655…2a6f
4 touches
1 conflict
0x5cfec795…7c0e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00532bf5…5711
0x754704…b603
2 touches
0 conflicts
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
10 conflicts on slot 0x806c6904e3…af3d63
Audit this contract →
← previous block·next block →recent activity