← previous blocknext block →recent activity
Analyzing
Block #100,020,610
19 transactions · 18 stateful · 2026-08-28 22:44:08 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,020,610 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w18w210w011w012w113w316w017w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
8 touches
6 conflicts
0x24bb46f7…3853
0x34b655…2a6f
8 touches
6 conflicts
0xa3686740…a19a
0x34b655…2a6f
8 touches
6 conflicts
0xf5741778…4892
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x90a8fb04…ff2b
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity