← previous blocknext block →recent activity
Analyzing
Block #98,566,194
13 transactions · 13 stateful · 2026-08-23 20:00:35 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,566,194 · 13 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
2w06w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb88ed4e…a342
0x34b655…2a6f
6 touches
3 conflicts
0x3ff23b62…0bea
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0x972d632b…dff1
0x34b655…2a6f
2 touches
0 conflicts
0x1686502b…a1d2
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x86dfd5…6a7d
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
3 conflicts on slot 0xeb88ed4e17…eaa342
Audit this contract →
← previous block·next block →recent activity