← previous blocknext block →recent activity
Analyzing
Block #98,286,884
14 transactions · 14 stateful · 2026-08-22 20:22:19 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,286,884 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w06w07w18w19w111w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecea23db…7fb9
0x34b655…2a6f
4 touches
1 conflict
0x91e15734…da39
0x34b655…2a6f
4 touches
1 conflict
0xac1ef24c…244c
0x34b655…2a6f
4 touches
1 conflict
0xbaf77397…e798
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
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
1 conflict on slot 0xecea23db30…c07fb9
Audit this contract →
← previous block·next block →recent activity