← previous blocknext block →recent activity
Analyzing
Block #97,842,181
28 transactions · 25 stateful · 2026-08-21 06:51:29 UTC
Parallelism
79/100
Blocked
52%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,842,181 · 28 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
4w05w16w08w09w010w111w212w213w314w415w518w320w421w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x7753b200…57a7
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xec1d6663…6042
0x34b655…2a6f
8 touches
6 conflicts
0x2528e717…2a22
0x34b655…2a6f
6 touches
3 conflicts
0x503399b0…e5bd
0x34b655…2a6f
4 touches
1 conflict
0x90687d94…b524
0x34b655…2a6f
4 touches
1 conflict
0xac206e47…ef7d
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 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity