← previous blocknext block →recent activity
Analyzing
Block #100,079,089
20 transactions · 19 stateful · 2026-08-29 03:38:30 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,079,089 · 20 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
1w04w05w16w08w19w210w314w415w516w619w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdb510b9…2bc4
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
10 touches
10 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xce4a30d2…2169
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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 0xbdb510b933…722bc4
Audit this contract →
← previous block·next block →recent activity