← previous blocknext block →recent activity
Analyzing
Block #98,838,099
36 transactions · 27 stateful · 2026-08-24 19:12:07 UTC
Parallelism
89/100
Blocked
41%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,838,099 · 36 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w011w012w114w215w016w117w019w120w121w022w024w126w127w228w329w335w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf86f1759…7786
0x34b655…2a6f
8 touches
6 conflicts
0x8e66da19…66b6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9c6a9da2…c628
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
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 0xf86f17596c…ab7786
Audit this contract →
← previous block·next block →recent activity