← previous blocknext block →recent activity
Analyzing
Block #98,500,204
29 transactions · 21 stateful · 2026-08-23 14:16:13 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,500,204 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w010w112w217w318w119w120w021w125w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd1450d8e…475b
0x34b655…2a6f
6 touches
3 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xdf0cf99d…47ae
0x34b655…2a6f
5 touches
3 conflicts
0x7c93b38a…9e69
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity