← previous blocknext block →recent activity
Analyzing
Block #100,625,969
24 transactions · 21 stateful · 2026-08-31 01:34:19 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,625,969 · 24 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
1w04w15w06w18w09w110w214w215w316w418w119w521w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
10 touches
10 conflicts
0xf1218340…df46
0x34b655…2a6f
6 touches
3 conflicts
0x0e6f9f04…303f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0xb7aa9720…56df
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd1b40f29…9b9d
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 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity