← previous blocknext block →recent activity
Analyzing
Block #100,055,116
17 transactions · 16 stateful · 2026-08-29 01:37:49 UTC
Parallelism
47/100
Blocked
69%
Avg conflicts / tx
2.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,055,116 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w17w28w39w410w511w612w713w615w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb240b520…a88a
0x34b655…2a6f
14 touches
21 conflicts
0x602ccada…14d4
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x6f51dccd…fc90
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
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
21 conflicts on slot 0xb240b520db…67a88a
Audit this contract →
← previous block·next block →recent activity