← previous blocknext block →recent activity
Analyzing
Block #98,354,690
21 transactions · 20 stateful · 2026-08-23 02:03:29 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,354,690 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w19w210w312w414w315w416w519w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30908823…a62d
0x34b655…2a6f
8 touches
6 conflicts
0x68e5627d…6f8f
0x34b655…2a6f
8 touches
6 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0x2cef1eff…9f14
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x14cc77c7…69c4
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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 0x3090882336…22a62d
Audit this contract →
← previous block·next block →recent activity