← previous blocknext block →recent activity
Analyzing
Block #97,529,108
29 transactions · 27 stateful · 2026-08-20 04:21:36 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,529,108 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w08w09w110w011w113w214w315w016w318w119w120w422w427w528w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35c37635…11a6
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x25d909da…1722
0x34b655…2a6f
4 touches
1 conflict
0x2dcc0868…26bf
0x34b655…2a6f
4 touches
1 conflict
0x3a06aac2…c200
0x34b655…2a6f
4 touches
1 conflict
0x3caa301f…0285
0x34b655…2a6f
4 touches
1 conflict
0x3e2bbed5…de49
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
10 conflicts on slot 0x35c37635a4…5311a6
Audit this contract →
← previous block·next block →recent activity