← previous blocknext block →recent activity
Analyzing
Block #103,050,134
41 transactions · 32 stateful · 2026-09-08 13:22:25 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
1.07
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #103,050,134 · 41 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w18w29w010w115w317w218w120w229w331w532w433w534w635w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xdfa159d0…1576
0x065c9d…c394
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x59a133dd…7982
0x34b655…2a6f
8 touches
6 conflicts
0x8488f10f…9353
0x34ae4d…3fc5
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity