← previous blocknext block →recent activity
Analyzing
Block #99,874,145
16 transactions · 15 stateful · 2026-08-28 10:26:13 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,874,145 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w09w110w212w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21a1d259…eda5
0x34b655…2a6f
8 touches
6 conflicts
0x24b6091e…d294
0x34b655…2a6f
6 touches
3 conflicts
0xe7ad475a…0e41
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xbad4e90b…33a5
0x34b655…2a6f
6 touches
3 conflicts
0xe6ce8890…bd67
0x34b655…2a6f
6 touches
3 conflicts
0x7dfcf75c…20cc
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
6 conflicts on slot 0x21a1d2596d…58eda5
Audit this contract →
← previous block·next block →recent activity