← previous blocknext block →recent activity
Analyzing
Block #100,601,387
52 transactions · 34 stateful · 2026-08-30 23:30:40 UTC
Parallelism
87/100
Blocked
62%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,601,387 · 52 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w09w110w217w318w419w521w623w035w139w144w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xb240b520…a88a
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1d10f24a…2fb8
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 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: 0xf5b5f7f8…a36d70
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity