← previous blocknext block →recent activity
Analyzing
Block #98,439,203
19 transactions · 18 stateful · 2026-08-23 09:08:40 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,439,203 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w29w310w012w414w115w516w6
- 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
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x705ab4ae…0162
0x34b655…2a6f
7 touches
6 conflicts
0x13807d54…85db
0x34b655…2a6f
6 touches
3 conflicts
0x88e92ec7…696d
0x34b655…2a6f
6 touches
3 conflicts
0x96d3e741…c328
0x34b655…2a6f
5 touches
3 conflicts
0xae71aeba…7093
0x34b655…2a6f
5 touches
3 conflicts
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