← previous blocknext block →recent activity
Analyzing
Block #99,977,495
21 transactions · 18 stateful · 2026-08-28 19:07:01 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,977,495 · 21 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
2w03w15w06w07w111w112w214w116w017w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x8649e48f…941c
0xc8689a…ee79
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x143cd54f…c109
0x851145…3f07
4 touches
1 conflict
0x6676e4f3…6a9e
0x851145…3f07
4 touches
1 conflict
0xc448e273…c274
0x851145…3f07
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 0x6f132c01d5…7dcdcc
Audit this contract →
← previous block·next block →recent activity