← previous blocknext block →recent activity
Analyzing
Block #108,787,502
56 transactions · 44 stateful · 2026-09-28 15:31:20 UTC
Parallelism
61/100
Blocked
68%
Avg conflicts / tx
3.57
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #108,787,502 · 56 txs across 22 waves · depth 22
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w26w39w410w511w612w730w831w934w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
36 touches
153 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
32 touches
120 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
32 touches
120 conflicts
0x238d0a65…428b
0x37db7f…ec7b
32 touches
120 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
32 touches
120 conflicts
0x0d54fa3e…3b3c
0x34b655…2a6f
32 touches
120 conflicts
0x4c71d355…5ace
0x34b655…2a6f
32 touches
120 conflicts
0x6c09658a…d1d9
0x34b655…2a6f
32 touches
120 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
153 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity