← previous blocknext block →recent activity
Analyzing
Block #97,988,635
17 transactions · 14 stateful · 2026-08-21 19:20:30 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,988,635 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w08w19w110w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d01a6f6…7dbe
0x34b655…2a6f
4 touches
1 conflict
0xcc5d8997…432c
0x34b655…2a6f
4 touches
1 conflict
0xeca74ff3…a361
0x34b655…2a6f
4 touches
1 conflict
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0xf7633854…843e
0x34b655…2a6f
4 touches
1 conflict
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0xaa431b7f…9ebf
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 0x3d01a6f68c…fb7dbe
Audit this contract →
← previous block·next block →recent activity