← previous blocknext block →recent activity
Analyzing
Block #108,549,235
55 transactions · 46 stateful · 2026-09-27 19:31:09 UTC
Parallelism
73/100
Blocked
65%
Avg conflicts / tx
2.69
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #108,549,235 · 55 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w18w29w311w412w513w615w717w824w442w243w946w450w1051w1152w1253w1354w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
24 touches
66 conflicts
0xd89580ee…a7a0
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
12 touches
15 conflicts
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x482471ad…122f
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: 0x125f12a1…cda50b
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity