← previous blocknext block →recent activity
Analyzing
Block #100,918,207
32 transactions · 29 stateful · 2026-09-01 02:04:46 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
1.66
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,918,207 · 32 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
1w04w05w06w07w18w29w310w412w114w215w316w417w520w522w624w126w731w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55192654…91fe
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x6f0befc9…48e9
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xf5b5f7…6d70
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x6f28b0ee…246c
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xf76df566…dffd
0x34b655…2a6f
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: Perpl
15 conflicts on slot 0x551926541c…2e91fe
Audit this contract →
← previous block·next block →recent activity