← previous blocknext block →recent activity
Analyzing
Block #108,610,603
24 transactions · 20 stateful · 2026-09-28 00:40:15 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,610,603 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w29w310w411w518w122w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x0ddc998e…def8
0x34b655…2a6f
6 touches
3 conflicts
0x16d77246…bac5
0x34b655…2a6f
6 touches
3 conflicts
0x280aaa58…1c52
0x34b655…2a6f
6 touches
3 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
6 touches
3 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
6 touches
3 conflicts
0x4c71d355…5ace
0x34b655…2a6f
6 touches
3 conflicts
0x6c09658a…d1d9
0x34b655…2a6f
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity