← previous blocknext block →recent activity
Analyzing
Block #100,560,410
12 transactions · 12 stateful · 2026-08-30 20:04:32 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,560,410 · 12 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
2w05w06w18w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6324ccc9…14fd
0x34b655…2a6f
6 touches
3 conflicts
0x733c7779…a647
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3acf9416…7ddc
0x34b655…2a6f
2 touches
0 conflicts
0x53e056e3…c862
0x34b655…2a6f
2 touches
0 conflicts
0x586b9498…a2cc
0x34b655…2a6f
2 touches
0 conflicts
0x625b3258…fbcd
0x34b655…2a6f
2 touches
0 conflicts
0x6fba5536…cc75
0x34b655…2a6f
2 touches
0 conflicts
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 0x6324ccc962…7f14fd
Audit this contract →
← previous block·next block →recent activity