← previous blocknext block →recent activity
Analyzing
Block #99,192,117
17 transactions · 14 stateful · 2026-08-26 00:59:56 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,192,117 · 17 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
3w05w06w19w210w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68531239…e9a3
0x34b655…2a6f
6 touches
3 conflicts
0x4fdef8ec…a320
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x62bce8b9…c530
0x34b655…2a6f
3 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 0x68531239f9…5ae9a3
Audit this contract →
← previous block·next block →recent activity