← previous blocknext block →recent activity
Analyzing
Block #100,159,673
20 transactions · 17 stateful · 2026-08-29 10:24:22 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,159,673 · 20 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
1w02w03w15w17w110w211w212w316w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
8 touches
6 conflicts
0x20917477…6135
0x34b655…2a6f
6 touches
3 conflicts
0xf98c943e…7c44
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
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 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity