← previous blocknext block →recent activity
Analyzing
Block #100,706,628
25 transactions · 19 stateful · 2026-08-31 08:20:03 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,706,628 · 25 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
3w07w19w010w011w112w213w016w317w419w520w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedee7e09…6888
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0xff694974…7e0c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x49b0842d…0a93
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 0xedee7e090f…056888
Audit this contract →
← previous block·next block →recent activity