← previous blocknext block →recent activity
Analyzing
Block #100,620,637
34 transactions · 24 stateful · 2026-08-31 01:07:30 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,620,637 · 34 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
1w04w15w18w29w313w415w016w121w422w523w629w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
10 touches
10 conflicts
0x32e6354f…5f73
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x15f332d1…455a
0x34b655…2a6f
6 touches
3 conflicts
0xfac61869…a562
0x1b6862…e19c
4 touches
1 conflict
0x3dd02e95…7536
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity