← previous blocknext block →recent activity
Analyzing
Block #108,951,798
28 transactions · 27 stateful · 2026-09-29 05:21:35 UTC
Parallelism
86/100
Blocked
30%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,951,798 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w111w212w213w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6deafb5…5c25
0x34b655…2a6f
8 touches
6 conflicts
0x3e04662b…0da6
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xed4377a5…4890
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x37e8223b…bb6e
0xd32edf…ff58
7 touches
6 conflicts
0x4b2a9f64…3a39
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
6 conflicts on slot 0xf6deafb553…9e5c25
Audit this contract →
← previous block·next block →recent activity