← previous blocknext block →recent activity
Analyzing
Block #108,466,413
22 transactions · 19 stateful · 2026-09-27 12:34:13 UTC
Parallelism
55/100
Blocked
58%
Avg conflicts / tx
1.95
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,466,413 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w613w619w721w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
16 touches
28 conflicts
0x73912233…4586
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0xa0632a87…9d5b
0x34b655…2a6f
14 touches
21 conflicts
0xe3541e6b…114a
0xd32edf…ff58
13 touches
21 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity