← previous blocknext block →recent activity
Analyzing
Block #98,203,272
23 transactions · 18 stateful · 2026-08-22 13:21:41 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,203,272 · 23 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
2w03w04w15w26w312w313w414w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xe71e6fec…c88b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x450f5a60…bf64
0x34b655…2a6f
2 touches
0 conflicts
0x6a2ca7be…18a8
0x34b655…2a6f
2 touches
0 conflicts
0x8b501dcf…1040
0x34b655…2a6f
2 touches
0 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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity