← previous blocknext block →recent activity
Analyzing
Block #98,443,617
17 transactions · 13 stateful · 2026-08-23 09:30:53 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,443,617 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3684e08…c96a
0x34b655…2a6f
4 touches
1 conflict
0xadcc6a38…4ef1
0x34b655…2a6f
4 touches
1 conflict
0x8bb4e35b…2c9e
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2507094f…eab4
0x34b655…2a6f
2 touches
0 conflicts
0x39da55ef…42d5
0x34b655…2a6f
2 touches
0 conflicts
0x68c740e2…58d6
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xe3684e088a…5fc96a
Audit this contract →
← previous block·next block →recent activity