← previous blocknext block →recent activity
Analyzing
Block #108,533,838
36 transactions · 34 stateful · 2026-09-27 18:13:37 UTC
Parallelism
53/100
Blocked
68%
Avg conflicts / tx
4.53
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #108,533,838 · 36 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w16w08w19w213w314w415w516w617w718w819w920w1021w1122w1223w1325w1530w131w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
30 touches
105 conflicts
0x00000000…001d
0x1b6862…e19c
28 touches
91 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
28 touches
91 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…0012
0x1b6862…e19c
28 touches
91 conflicts
0xd49d0379…e831
0xd32edf…ff58
27 touches
91 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
26 touches
78 conflicts
0xcbfe7421…3168
0x34b655…2a6f
22 touches
55 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
105 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity