← previous blocknext block →recent activity
Analyzing
Block #99,779,061
23 transactions · 21 stateful · 2026-08-28 02:25:15 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,779,061 · 23 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
1w03w04w05w06w18w19w212w313w115w118w021w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7960be3…7f19
0x34b655…2a6f
6 touches
3 conflicts
0x6ff07b44…ab99
0x40c49f…2af0
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xe5c4bbfe…6a57
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x3db38b2b…818d
0x40c49f…2af0
4 touches
1 conflict
0x0bd5255a…a83a
0x34b655…2a6f
4 touches
1 conflict
0x230d0904…a656
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 0xb7960be3f0…c77f19
Audit this contract →
← previous block·next block →recent activity