← previous blocknext block →recent activity
Analyzing
Block #98,735,710
14 transactions · 14 stateful · 2026-08-24 10:36:39 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,735,710 · 14 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
5w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xded216ce…191a
0xa6afd3…d132
4 touches
1 conflict
0x04be98f0…f405
0x34b655…2a6f
2 touches
0 conflicts
0x067c87f1…e98a
0x34b655…2a6f
2 touches
0 conflicts
0x122e2052…2bfe
0x34b655…2a6f
2 touches
0 conflicts
0x1a0aedf0…23d8
0x34b655…2a6f
2 touches
0 conflicts
0x1b7f7926…4ad2
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity