← previous blocknext block →recent activity
Analyzing
Block #98,272,410
23 transactions · 19 stateful · 2026-08-22 19:09:30 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,272,410 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w010w211w312w113w114w419w020w121w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0xd6ab949f…82f0
0x34b655…2a6f
6 touches
3 conflicts
0xaf30c163…0fb6
0x34b655…2a6f
6 touches
3 conflicts
0xb3037bed…6b7c
0x34b655…2a6f
6 touches
3 conflicts
0x49b0842d…0a93
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity