← previous blocknext block →recent activity
Analyzing
Block #100,079,964
20 transactions · 20 stateful · 2026-08-29 03:42:55 UTC
Parallelism
60/100
Blocked
35%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,079,964 · 20 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
6w08w19w210w311w412w514w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
8 touches
6 conflicts
0xe4af4c87…9964
0x34b655…2a6f
6 touches
3 conflicts
0xb8a78c5a…e473
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x2b43dd7d…7f99
0x34b655…2a6f
4 touches
1 conflict
0x4f3a6b4a…3819
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity