← previous blocknext block →recent activity
Analyzing
Block #98,674,713
20 transactions · 20 stateful · 2026-08-24 05:25:48 UTC
Parallelism
50/100
Blocked
55%
Avg conflicts / tx
1.4
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,674,713 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w411w512w613w716w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x386d08f4…5a01
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xbb0b001d…e852
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 0x386d08f44a…fc5a01
Audit this contract →
← previous block·next block →recent activity