← previous blocknext block →recent activity
Analyzing
Block #98,848,903
24 transactions · 23 stateful · 2026-08-24 20:06:28 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,848,903 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w19w011w112w013w017w118w219w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x11560115…bfc2
0x34b655…2a6f
6 touches
3 conflicts
0xb9d2cf20…a668
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xfe20cb8f…f03d
0x34b655…2a6f
5 touches
3 conflicts
0x81d96242…fbf9
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity