← previous blocknext block →recent activity
Analyzing
Block #108,942,075
28 transactions · 22 stateful · 2026-09-29 04:32:30 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,942,075 · 28 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
1w02w13w24w37w08w19w415w116w520w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b780b26…f5ff
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x1faeed20…190f
0x34b655…2a6f
10 touches
10 conflicts
0xada087b9…4aca
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
8 touches
6 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
8 touches
6 conflicts
0x88fc2a68…3918
0x34b655…2a6f
8 touches
6 conflicts
0xfc8c9734…8019
0x34b655…2a6f
8 touches
6 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 0x8b780b2668…85f5ff
Audit this contract →
← previous block·next block →recent activity