← previous blocknext block →recent activity
Analyzing
Block #100,738,155
28 transactions · 24 stateful · 2026-08-31 10:58:39 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,738,155 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w17w29w010w113w214w318w419w520w623w124w727w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf38a3927…ad62
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x3908df30…26f8
0x34b655…2a6f
10 touches
10 conflicts
0x4ce3a232…eea1
0x34b655…2a6f
8 touches
6 conflicts
0xafb22303…6db2
0x34b655…2a6f
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0x5702fa73…faf6
0x34b655…2a6f
5 touches
3 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
21 conflicts on slot 0xf38a392760…8fad62
Audit this contract →
← previous block·next block →recent activity