← previous blocknext block →recent activity
Analyzing
Block #108,619,613
41 transactions · 36 stateful · 2026-09-28 01:25:38 UTC
Parallelism
83/100
Blocked
67%
Avg conflicts / tx
1.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,619,613 · 41 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
1w02w13w04w05w17w28w39w410w514w315w417w636w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0x125f12…a50b
14 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity