← previous blocknext block →recent activity
Analyzing
Block #98,736,024
20 transactions · 20 stateful · 2026-08-24 10:38:14 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,736,024 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w18w29w310w314w015w118w419w5
- 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
0xaf1337eb…92c3
0x34b655…2a6f
6 touches
3 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
6 touches
3 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x58fb4cd2…ef29
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