← previous blocknext block →recent activity
Analyzing
Block #108,946,831
25 transactions · 24 stateful · 2026-09-29 04:56:34 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
1.44
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,946,831 · 25 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
1w03w14w26w38w09w211w412w513w614w717w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0056
0x1b6862…e19c
6 touches
3 conflicts
0x106f80f5…d419
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity