← previous blocknext block →recent activity
Analyzing
Block #99,307,960
12 transactions · 11 stateful · 2026-08-26 10:42:47 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,307,960 · 12 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
4w05w06w17w28w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38111b8a…f6b7
0x34b655…2a6f
6 touches
3 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
6 touches
3 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0xf38a3927…ad62
0x34b655…2a6f
4 touches
1 conflict
0xf5a1b40e…5a12
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
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 0x38111b8aa6…65f6b7
Audit this contract →
← previous block·next block →recent activity