← previous blocknext block →recent activity
Analyzing
Block #108,113,559
24 transactions · 23 stateful · 2026-09-26 06:58:24 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,113,559 · 24 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
1w02w13w04w06w19w010w111w112w013w114w215w118w019w120w221w322w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0x9471fcdc…fc4a
0xd32edf…ff58
5 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x532af68d…503d
0x34b655…2a6f
4 touches
1 conflict
0x59f14360…45d6
0x34b655…2a6f
4 touches
1 conflict
0x6e360a5d…8836
0x34b655…2a6f
4 touches
1 conflict
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity