← previous blocknext block →recent activity
Analyzing
Block #98,490,226
25 transactions · 24 stateful · 2026-08-23 13:25:44 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.44
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,490,226 · 25 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
1w02w03w14w07w08w111w115w216w317w418w120w522w724w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x627738d1…db02
0x34b655…2a6f
10 touches
10 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 conflicts
0x67a21428…bdd5
0x34b655…2a6f
4 touches
1 conflict
0x71fad9ce…c11f
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity