← previous blocknext block →recent activity
Analyzing
Block #98,071,183
19 transactions · 19 stateful · 2026-08-22 02:16:23 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,071,183 · 19 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
1w07w08w19w010w111w212w313w414w415w417w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0xa56ae218…1fc5
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3fff7ccd…5a48
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0x6b09fb8c…5518
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
3 conflicts on slot 0x629109215a…273016
Audit this contract →
← previous block·next block →recent activity