← previous blocknext block →recent activity
Analyzing
Block #98,640,831
16 transactions · 16 stateful · 2026-08-24 02:29:12 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,640,831 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w410w512w614w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa02838a3…bc54
0x34b655…2a6f
6 touches
3 conflicts
0x6dedaff6…161b
0x34b655…2a6f
6 touches
3 conflicts
0x12b2b8fa…0ca4
0x34b655…2a6f
6 touches
3 conflicts
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity