← previous blocknext block →recent activity
Analyzing
Block #97,731,619
14 transactions · 14 stateful · 2026-08-20 21:33:15 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,731,619 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w07w111w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33b5035a…d1c6
0x34b655…2a6f
4 touches
1 conflict
0x3d83aa49…93b7
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x88c076d4…6c76
0x34b655…2a6f
4 touches
1 conflict
0x8a1feb08…dea9
0x34b655…2a6f
4 touches
1 conflict
0x913c9afa…4206
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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
1 conflict on slot 0x33b5035ada…70d1c6
Audit this contract →
← previous block·next block →recent activity