← previous blocknext block →recent activity
Analyzing
Block #97,396,756
23 transactions · 18 stateful · 2026-08-19 17:13:42 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,396,756 · 23 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
1w05w16w08w09w110w212w213w314w415w416w517w620w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x3750b746…5a9e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6bc293e9…556e
0x34b655…2a6f
4 touches
1 conflict
0x6f6aa736…a698
0x34b655…2a6f
4 touches
1 conflict
0x9b2edc72…6af8
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
15 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity