← previous blocknext block →recent activity
Analyzing
Block #97,511,250
23 transactions · 23 stateful · 2026-08-20 02:51:46 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,511,250 · 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
3w05w06w08w19w210w211w313w414w516w518w119w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8902ba1f…f4b6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5cfec795…7c0e
0x34b655…2a6f
6 touches
3 conflicts
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2dcc0868…26bf
0x34b655…2a6f
4 touches
1 conflict
0x35c37635…11a6
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
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 0x8902ba1fb5…70f4b6
Audit this contract →
← previous block·next block →recent activity