← previous blocknext block →recent activity
Analyzing
Block #96,124,250
19 transactions · 16 stateful · 2026-08-15 05:49:42 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,124,250 · 19 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
1w02w13w04w18w09w112w213w214w015w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1976b30…18f0
0x34b655…2a6f
8 touches
6 conflicts
0x0fe1e6e0…f553
0x34b655…2a6f
4 touches
1 conflict
0x1544d128…23e7
0x34b655…2a6f
4 touches
1 conflict
0x4728ff48…c029
0x34b655…2a6f
4 touches
1 conflict
0x5f689f7f…d18e
0x34b655…2a6f
4 touches
1 conflict
0x69c491e3…98d9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x85e59464…9104
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 0xb1976b3064…db18f0
Audit this contract →
← previous block·next block →recent activity