← previous blocknext block →recent activity
Analyzing
Block #100,020,135
21 transactions · 20 stateful · 2026-08-28 22:41:45 UTC
Parallelism
71/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,020,135 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w09w110w011w112w213w314w115w316w417w518w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc82ac719…b47e
0x34b655…2a6f
10 touches
10 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0x9a9383a9…6bc7
0x34b655…2a6f
4 touches
1 conflict
0xb51374d2…29ed
0x34b655…2a6f
4 touches
1 conflict
0xb5c7c6aa…fdba
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
10 conflicts on slot 0xc82ac71961…06b47e
Audit this contract →
← previous block·next block →recent activity