← previous blocknext block →recent activity
Analyzing
Block #97,819,838
19 transactions · 19 stateful · 2026-08-21 04:58:31 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,819,838 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w09w110w211w212w314w215w316w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xbe6d0f1c…20a0
0x34b655…2a6f
6 touches
3 conflicts
0x343cc1e5…3df0
0x34b655…2a6f
4 touches
1 conflict
0x3c369b9c…e94d
0x34b655…2a6f
4 touches
1 conflict
0x4119aba4…5027
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7316dc00…c16a
0x34b655…2a6f
4 touches
1 conflict
0x7975e059…379b
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 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity