← previous blocknext block →recent activity
Analyzing
Block #101,135,235
73 transactions · 52 stateful · 2026-09-01 20:16:57 UTC
Parallelism
71/100
Blocked
79%
Avg conflicts / tx
4.7
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #101,135,235 · 73 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w611w712w821w922w1023w1124w1225w1326w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
40 touches
190 conflicts
0xaad6be10…0801
0x2a68ba…90c5
30 touches
105 conflicts
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
10 touches
10 conflicts
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
190 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity