← previous blocknext block →recent activity
Analyzing
Block #98,737,305
26 transactions · 19 stateful · 2026-08-24 10:44:40 UTC
Parallelism
81/100
Blocked
58%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,737,305 · 26 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
1w02w13w25w06w17w015w116w117w220w321w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xe31cf99d…cb66
0x754704…b603
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x36743f6f…476b
0x3bd359…433a
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity