← previous blocknext block →recent activity
Analyzing
Block #98,206,561
27 transactions · 23 stateful · 2026-08-22 13:38:14 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,206,561 · 27 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
1w03w04w05w16w010w111w212w314w315w416w019w120w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68e5627d…6f8f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x0563d8c3…caaf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x68e5627d66…486f8f
Audit this contract →
← previous block·next block →recent activity