← previous blocknext block →recent activity
Analyzing
Block #100,567,614
14 transactions · 13 stateful · 2026-08-30 20:40:46 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,567,614 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w19w211w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0x41f621e0…9e98
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa8ce1783…6484
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf38a3927…ad62
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x6a67f152…81b1
0x065c9d…c394
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
3 conflicts on slot 0xcef70a965c…28db44
Audit this contract →
← previous block·next block →recent activity