← previous blocknext block →recent activity
Analyzing
Block #100,227,241
22 transactions · 20 stateful · 2026-08-29 16:04:29 UTC
Parallelism
68/100
Blocked
30%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,227,241 · 22 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
1w08w09w111w213w314w415w519w020w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x5a548af5…0eb0
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xa94a14cf…866c
0x34b655…2a6f
7 touches
6 conflicts
0x83f3d320…fb59
0x34b655…2a6f
6 touches
3 conflicts
0x9a9383a9…6bc7
0x34b655…2a6f
6 touches
3 conflicts
0xfa3d71b4…937f
0x34b655…2a6f
6 touches
3 conflicts
0x35b89cd8…5092
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity