← previous blocknext block →recent activity
Analyzing
Block #100,586,443
20 transactions · 16 stateful · 2026-08-30 22:15:29 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,586,443 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w314w415w517w518w019w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21791706…411d
0x34b655…2a6f
10 touches
10 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
8 touches
6 conflicts
0xce74d807…8716
0x34b655…2a6f
8 touches
6 conflicts
0x08118215…4081
0x34b655…2a6f
8 touches
6 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
6 touches
3 conflicts
0x0ed7cc0b…ee52
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 0x2179170630…e5411d
Audit this contract →
← previous block·next block →recent activity