← previous blocknext block →recent activity
Analyzing
Block #108,627,208
20 transactions · 20 stateful · 2026-09-28 02:03:52 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
2.1
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,627,208 · 20 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
1w02w03w14w26w17w28w39w410w511w612w713w814w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x280aaa58…1c52
0x34b655…2a6f
16 touches
28 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
16 touches
28 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
16 touches
28 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
16 touches
28 conflicts
0x434ddf72…de6a
0x34b655…2a6f
16 touches
28 conflicts
0x4c71d355…5ace
0x34b655…2a6f
16 touches
28 conflicts
0x55a37f69…aece
0x34b655…2a6f
16 touches
28 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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity