← previous blocknext block →recent activity
Analyzing
Block #108,641,459
20 transactions · 19 stateful · 2026-09-28 03:15:41 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,641,459 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w19w212w213w314w315w419w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a6bd235…f40b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xdd77da90…6df4
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x479ce48c…fa1a
0x1b6862…e19c
6 touches
3 conflicts
0xa38c430a…e3cb
0x34b655…2a6f
6 touches
3 conflicts
0xc16cbd48…5891
0xd32edf…ff58
5 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
3 conflicts on slot 0x6a6bd235b4…fdf40b
Audit this contract →
← previous block·next block →recent activity