← previous blocknext block →recent activity
Analyzing
Block #100,154,945
22 transactions · 20 stateful · 2026-08-29 10:00:34 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,154,945 · 22 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
1w04w05w17w215w116w017w218w119w320w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf98c943e…7c44
0x34b655…2a6f
8 touches
6 conflicts
0x08f39e39…ed46
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x4b24225e…5a6b
0x34b655…2a6f
4 touches
1 conflict
0x5ed1f9d0…fc7f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
6 conflicts on slot 0xf98c943e1d…327c44
Audit this contract →
← previous block·next block →recent activity