← previous blocknext block →recent activity
Analyzing
Block #100,850,542
58 transactions · 48 stateful · 2026-08-31 20:24:25 UTC
Parallelism
60/100
Blocked
79%
Avg conflicts / tx
2.6
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #100,850,542 · 58 txs across 23 waves · depth 23
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
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w48w59w611w135w741w342w244w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xaad6be10…0801
0x2a68ba…90c5
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
10 touches
10 conflicts
0x5f77d607…2c84
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity