← previous blocknext block →recent activity
Analyzing
Block #100,110,020
25 transactions · 23 stateful · 2026-08-29 06:14:14 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,110,020 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w08w09w112w113w214w315w417w318w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x944a1493…fdd4
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd6370b2a…08cb
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5fde4971…aac9
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0x5c8a8db2…8a6d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x944a149310…bffdd4
Audit this contract →
← previous block·next block →recent activity