← previous blocknext block →recent activity
Analyzing
Block #108,299,627
37 transactions · 32 stateful · 2026-09-26 22:34:50 UTC
Parallelism
76/100
Blocked
66%
Avg conflicts / tx
1.73
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,299,627 · 37 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w512w013w115w016w117w218w319w420w522w623w725w634w735w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x3cf5ed4a…c35d
0x34b655…2a6f
14 touches
21 conflicts
0x3643d7c6…4925
0x34b655…2a6f
12 touches
15 conflicts
0x366a19b0…f065
0x34b655…2a6f
12 touches
15 conflicts
0x3737da55…2063
0x34b655…2a6f
12 touches
15 conflicts
0x71a923ba…41eb
0x34b655…2a6f
12 touches
15 conflicts
0x9cc778a3…2452
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity