← previous blocknext block →recent activity
Analyzing
Block #100,605,421
28 transactions · 19 stateful · 2026-08-30 23:50:58 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,605,421 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w110w013w116w020w122w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ccfe55c…de03
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x5f498f29…84db
0x40c49f…2af0
4 touches
1 conflict
0xa68fa99d…0358
0x40c49f…2af0
4 touches
1 conflict
0xc34ee2a2…8a32
0x40c49f…2af0
4 touches
1 conflict
0x5934b407…e058
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0x4ccfe55c0b…fbde03
Audit this contract →
← previous block·next block →recent activity