← previous blocknext block →recent activity
Analyzing
Block #98,999,922
21 transactions · 20 stateful · 2026-08-25 08:46:38 UTC
Parallelism
86/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,999,922 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w111w112w013w115w016w119w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a34f692…092b
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xf3981be5…2c47
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x6a34f6920d…95092b
Audit this contract →
← previous block·next block →recent activity