← previous blocknext block →recent activity
Analyzing
Block #98,069,378
25 transactions · 23 stateful · 2026-08-22 02:07:18 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,069,378 · 25 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
1w02w03w16w07w18w210w011w112w214w016w117w218w319w320w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0x705ab4ae…0162
0x34b655…2a6f
6 touches
3 conflicts
0xa59f1ca5…5f09
0x065c9d…c394
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x2c97e962…ce1d
0x34b655…2a6f
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity