← previous blocknext block →recent activity
Analyzing
Block #101,992,418
34 transactions · 28 stateful · 2026-09-04 20:13:31 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
2.06
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #101,992,418 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w110w212w013w114w020w021w123w024w125w226w327w428w529w630w731w832w933w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x89aa10a6…265b
0xd32edf…ff58
5 touches
3 conflicts
0xcfe06a18…b5b5
0x34ae4d…3fc5
4 touches
1 conflict
0xd8fd2add…50fc
0x34ae4d…3fc5
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity