← previous blocknext block →recent activity
Analyzing
Block #103,040,162
26 transactions · 25 stateful · 2026-09-08 12:32:14 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,040,162 · 26 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
3w04w16w09w213w114w215w316w317w422w124w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac389ba9…8b45
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x3ff1d113…b6d4
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5e3f894e…634a
0x065c9d…c394
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0008
0x8f889b…868c
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
15 conflicts on slot 0xac389ba9d1…e18b45
Audit this contract →
← previous block·next block →recent activity